PK91946: JVM HANG DUE TO DEADLOCK [DEPLOYMENT MANAGER HANGS ON STARTUP DUE TO DEADLOCK]

6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• JVM hang due to deadlock [Deployment Manager hangs on startup
  due to deadlock since fixpack23 Update]
  
  From the native_stdout.log:
  
  Found one Java-level deadlock:
  =============================
  "server.startup : 1":
    waiting to lock monitor 0x00354e20 (object 0x80800408, a
  org.eclipse.
  osgi.internal.baseadaptor.DefaultClassLoader),
    which is held by "server.startup : 0"
  "server.startup : 0":
    waiting to lock monitor 0x00354880 (object 0x80801080, a
  org.eclipse.
  osgi.internal.baseadaptor.DefaultClassLoader),
    which is held by "server.startup : 1"
  

Local fix

• L3 provided testfix to client.
  (6.1.0.23-WS-WAS-IFPMR_38974_344_000.pak)
  
  alongwith with steps to verify the testfix.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V6.1                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: The Application Server hangs on         *
  *                      start up due to a deadlock.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When loading classes from OSGI bundles, the class loader for
  the bundle is locked. Circular dependencies between bundles
  can cause class loading to deadlock as a group of bundle
  class loaders wait on each other.
  

Problem conclusion

• Using more fine grained locking on the class name, rather than
  class loader, deadlocks from circular dependencies can be
  avoided.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.1.0.29.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R61A PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP