Fix (APAR): PK41694 Status: Fix Release: 6.1.0.7 Operating System: AIX,HP-UX,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,Solaris,Windows Supersedes Fixes: CMVC Defect: PK41694 Byte size of APAR: 10212 Date: 2007-05-23 Abstract: If there are two simultaneous operations, like workspace-invoke and workspace-release then a deadlock in workspace might occur. Description/symptom of problem: PK41694 resolves the following problem: ERROR DESCRIPTION: DeadLock in WorkSpace. LOCAL FIX: PROBLEM SUMMARY USERS AFFECTED: IBM Websphere Application Server version 6.0 and 6.1 users. PROBLEM DESCRIPTION: If there are two simultaneous operations, like workspace-invoke and workspace-release then a deadlock in workspace might occur. RECOMMENDATION: None (1) Invoke workspace thread locks the RepositoryContext object and is waiting for the WorkSpaceManager object (2) Whereas the release thread locks the WorkSpaceManager object and is waiting for the RepositoryContext object in order to finish its task and release the WorkSpaceManager object. So both the tasks are waiting for a locked resource forever. Deadlock 1LKDEADLOCK Deadlock detected 2LKDEADLOCKTHR Thread "SoapConnectorThreadPool : 304" (0x0000000114BFEC00) 3LKDEADLOCKWTR is waiting for: 4LKDEADLOCKMON sys_mon_t:0x000000011527A4B0 infl_mon_t: 0x000000011527A500: 4LKDEADLOCKOBJ com/ibm/ws/sm/workspace/impl/ WorkSpaceManagerImpl@070000000280C4B0/ 070000000280C4C8: 3LKDEADLOCKOWN which is owned by: 2LKDEADLOCKTHR Thread "SoapConnectorThreadPool : 315" (0x000000011500EC00) 3LKDEADLOCKWTR which is waiting for: 4LKDEADLOCKMON sys_mon_t:0x0000000115279190 infl_mon_t: 0x00000001152791E0: 4LKDEADLOCKOBJ com/ibm/ws/sm/workspace/ impl/RepositoryContextImpl@ 0700000009008058/0700000009008070: 3LKDEADLOCKOWN which is owned by: 2LKDEADLOCKTHR Thread "SoapConnectorThreadPool : 304" (0x0000000114BFEC00) XMTHREADINFO SoapConnectorThreadPool : 315" (TID:0x000000011500EC00, sys_thread_t:0x0000000115750C50, state:B, native ID:0x00000000000541B5) prio=5 4XESTACKTRACE at com/ibm/ws/sm/workspace/ impl/WorkSpaceImpl.release (WorkSpaceImpl.java:380(Compiled Code)) 4XESTACKTRACE at com/ibm/ws/sm/workspace/impl/ WorkSpaceImpl.remove(WorkSpaceImpl.java:370 3XMTHREADINFO "SoapConnectorThreadPool : 304" (TID:0x0000000114BFEC00, sys_thread_t:0x0000000114AFBB30, state:B, native ID:0x00000000000252F3) prio=5 com/ibm/ws/management/configservice/ WorkspaceHelper.getWorkspace(WorkspaceHelper.java:79(Compiled Code)) 4XESTACKTRACE at com/ibm/ws/management/configservice/ WorkspaceHelper.getDocAccessor(WorkspaceHelper.java:182(Compiled Code)) 4XESTACKTRACE at com/ibm/ws/management/configservice/MOFUtil. convertToEObject(MOFUtil.java:114(Compiled PROBLEM CONCLUSION: Replaced method level synchronization with Synchronized blocks in Workspace code. The fix for this APAR is currently targeted for inclusion in service pack 6.0.2.21 and 6.1.0.11 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) __ 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 PKxxxxx.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 (PKxxxxx.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 (PKxxxxx.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: