Fix (APAR): PK35285 Status: Fix Release: 6.0.2.9,6.0.2.8,6.0.2.7,6.0.2.6,6.0.2.5,6.0.2.4,6.0.2.3,6.0.2.2,6.0.2.15,6.0.2.13,6.0.2.11 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,OS/390,OS/400,Solaris,Windows,z/OS Supersedes Fixes: CMVC Defect: PK35285 Byte size of APAR: 13585 Date: 2006-12-07 Abstract: CWSIV0773E exceptions are thrown indicating that the messaging engine is not started. Description/symptom of problem: PK35285 resolves the following problem: ERROR DESCRIPTION: When MDBs have been installed, the following error is seen in the messaging engine: CWSIV0773E: The exception javax.resource.ResourceException: CWSIV0950E: An internal error occurred. The exception com.ibm.websphere.sib.exception.SIResourceException: CWSIP0211E: messaging engine clus1.001-SCA.SYSTEM.qaxs16Node02Cell.Bus on bus SCA.SYSTEM.qaxs16Node02Cell.Bus is not started. was thrown while attempting to create a connection on factory com.ibm .ws.sib.processor.impl.MessageProcessor@413214c8. was thrown when processing the updated configuration for messaging engine clus1.001-SCA.SYSTEM.qaxs16Node02Cell.Bus on bus SCA.SYSTEM.qaxs16Node02Cell.Bus for endpoint activation [com.ibm.ws.sib.ra.inbound.impl. SibRaStaticDestinationEndpointActivation@7984d488 ]>]> ] LOCAL FIX: PROBLEM SUMMARY USERS AFFECTED: Users of WebSphere default messaing, who have promoted a server with installed applications into a cluster. PROBLEM DESCRIPTION: CWSIV0773E exceptions are thrown indicating that the messaging engine is not started. RECOMMENDATION: None During messaging engine configuration reload (message CWSID0019I), a javax.resource.ResourceException is thrown indicating that the messaging engine is not started. After this error has occurred, the messaging engines starts successfully. The error was due to the method that implements the reload expecting the messaging engine to be running, when this is not always the case. PROBLEM CONCLUSION: The method that handles the reload has been updated to handle the case where the messaging engine is not running. Directions to apply fix: Fix applies to Editions: Release 6.0 __ Application Server (Express or BASE) __ Network Deployment (ND) __ WebSphere Business Integration Server Foundation (WBISF) __ Edge Components __ Developer __ Extended Deployment (XD) Install Fix to: Method: __ Application Server Nodes __ Deployment Manager Nodes __ Both NOTE: The user must: * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 For detailed instructions to Extract the Update Installer see the following Technote: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400 1) Copy 6.0.2-WS-WAS-IFPK35285.pak file directly to the maintenance directory 2) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to. 3) Launch Update Installer 4) Enter the installation location of the WebSphere product you want to update. 5) Select the "Install maintenance package" operation. 6) Enter the file name of the maintenance package to install (6.0.2-WS-WAS-IFPK35285.pak file which was copied in the maintenance directory). 7) Install the maintenance package. 8) Restart WebSphere Directions to remove fix: NOTE: * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED * DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED * YOU MAY REAPPLY ANY REMOVED FIX Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied. 1) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against. 2) Start Update Installer 3) Enter the installation location of the WebSphere product you want to remove the fix. 4) Select "Uninstall maintenance package" operation. 5) Enter the file name of the maintenance package to uninstall (6.0.2-WS-WAS-IFPK35285.pak). 6) UnInstall maintenance package. 7) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere. Additional Information: