Fix (APAR): PK50802 Status: Fix Release: 6.1.0.9,6.1.0.7,6.1.0.5,6.1.0.3,6.1.0.2,6.1.0.11,6.1.0.1,6.1,6.0.2.21,6.0.2.19,6.0.2.17,6.0.2.15,6.0.2.13,6.0.2.11 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux zSeries,OS/400,Solaris,Windows Supersedes Fixes: 602 PREREQS OF PK30589 AND PK39804 6.1 PREREQS OF PK30589 AND PK39804 CMVC Defect: PK50802 Byte size of APAR: 183793 Date: 2007-10-03 Abstract: An HMGR5008 message is logged. Deadlock may occur if a Core Group Bridge process ends abnormally. Description/symptom of problem: PK50802 resolves the following problem: ERROR DESCRIPTION: There is deadlock in HAManager code: The deadlock seen in javacore: - 1LKDEADLOCK Deadlock detected !!! NULL --------------------- NULL 2LKDEADLOCKTHR Thread "HAManager.thread.pool : 0" (0x11C50E3C8) 3LKDEADLOCKWTR is waiting for: 4LKDEADLOCKMON sys_mon_t:0x11DB73F50 infl_mon_t: 0x11EDA4210: 4LKDEADLOCKOBJ com.ibm.ws.hamanager.datastack.DataStackImpl@70000000C01BA10/700 00000C01BA20: 3LKDEADLOCKOWN which is owned by: 2LKDEADLOCKTHR Thread "ThreadManager.JobsProcessorThread.ApplicationThread.0" (0x11C5040C8) 3LKDEADLOCKWTR which is waiting for: 4LKDEADLOCKMON sys_mon_t:0x11C3468F0 infl_mon_t: 0x00000000: 4LKDEADLOCKOBJ com.ibm.ws.hamanager.impl.ViewSynchronousHAGroup@70000000BF934F8 /70000000BF93508: 3LKDEADLOCKOWN which is owned by: 2LKDEADLOCKTHR Thread "HAManager.thread.pool : 0" (0x11C50E3C8) LOCAL FIX: None. PROBLEM SUMMARY USERS AFFECTED: Users of IBM WebSphere Application Server Network Deployment versions 6.0.2 and 6.1 PROBLEM DESCRIPTION: An HMGR5008 message is logged. Deadlock may occur if a Core Group Bridge process ends abnormally. RECOMMENDATION: None An HMGR5008 message is logged, indicating that a state change notification has been received, but contains no data. An unusual condition has occurred. The HA Manager coordinator initiated a state rebuild, but the rebuild was interrupted due to a secondary failure, which caused a second DCS view change during the rebuild. PROBLEM CONCLUSION: The HA Manager coordinator has been changed to handle the interrupted state rebuild properly. State change messages that are sent after the rebuild completes will now account for the interrupted rebuild. The fix for this APAR is currently targeted for inclusion in fixpacks 6.0.2.25 and 6.1.0.13. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Directions to apply fix: NOTE: Choose the: 1) Release the fix applies to 2) The Editions that apply 3) Delete the Editions & Methods that do not apply and this Note Fix applies to Editions: Release 6.0 __ Application Server (Express or BASE) _x_ 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 _x_ 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 PK50802.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 (PK50802.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 (PK50802.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: