IBM Support

PM11105: DEADLOCK OCCURS DURING DEFERRED EJB INITIALIZATION. RESULTS IN EJB METHOD INVOCATION FAILURE.

Fixes are available

6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
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
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Using the default configuration which is to defer the startup of
    EJBs, there is the possibility of a deadlock to occur when the
    EJBs are started.
    
    A javacore will show the following symptom:
    
    Found one Java-level deadlock:
    
    =============================
    "ORB.thread.pool : 4":
      waiting to lock monitor 0x00195240 (object 0xd900d4f0, a
    com.ibm.ejs.util.cache.WrapperBucket),
      which is held by "ORB.thread.pool : 0"
    "ORB.thread.pool : 0":
      waiting to lock monitor 0x00195438 (object 0xd93d6570, a
    com.ibm.ejs.csi.J2EENameImpl),
      which is held by "ORB.thread.pool : 4"
    
    
    Java stack information for the threads listed above:
    
    ===================================================
    "ORB.thread.pool : 4":
     at
    com.ibm.ws.runtime.component.EJBContainerImpl.initializeDeferred
    EJB(EJBContainerImpl.java:4439)
     - waiting to lock <0xd900d4f0> (a
    com.ibm.ejs.util.cache.WrapperBucket)
     at
    com.ibm.ejs.container.HomeOfHomes.getHome(HomeOfHomes.java:345)
     at
    com.ibm.ejs.container.HomeRecord.getHomeAndInitialize(HomeRecord
    .java:471)
     - locked <0xd93d6570> (a com.ibm.ejs.csi.J2EENameImpl)
     at
    com.ibm.ejs.container.HomeRecord.getPMInternalLocalHome(HomeReco
    rd.java:526)
     at
    com.ibm.ws.ejbpersistence.beanextensions.ConcreteBeanClassExtens
    ionImpl.getInternalHome(ConcreteBeanClassExtensionImpl.java:723)
     at
    com.ibm.ws.ejbpersistence.beanextensions.LinkMetadataImpl.getTar
    getHome(LinkMetadataImpl.java:125)
     at
    com.ibm.ws.ejbpersistence.beanextensions.ConcreteBeanStatefulIns
    tanceExtensionImpl.getHomeForLink(ConcreteBeanStatefulInsta
    nceExtensionImpl.java:1743)
     at
    ...
    
    
    "ORB.thread.pool : 0":
     at
    com.ibm.ejs.container.HomeRecord.getHomeAndInitialize(HomeRecord
    .java:470)
     - waiting to lock <0xd93d6570> (a com.ibm.ejs.csi.J2EENameImpl)
     at
    com.ibm.ejs.container.EJSContainer.getHomeWrapperCommon(EJSConta
    iner.java:1272)
     at
    com.ibm.ejs.container.EJSContainer.getHomeInstance(EJSContainer.
    java:1181)
     at
    com.ibm.ejs.container.EJSContainer.startBean(EJSContainer.java:1
    167)
     at
    com.ibm.ws.runtime.component.EJBContainerImpl.startBean(EJBConta
    inerImpl.java:3474)
     at
    com.ibm.ws.runtime.component.EJBContainerImpl.startAndBindHome(E
    JBContainerImpl.java:4753)
     at
    com.ibm.ws.runtime.component.EJBContainerImpl.initializeDeferred
    EJB(EJBContainerImpl.java:4528)
     - locked <0xd900d4f0> (a com.ibm.ejs.util.cache.WrapperBucket)
     at
    com.ibm.ejs.container.HomeOfHomes.getHome(HomeOfHomes.java:345)
     at
    com.ibm.ejs.container.HomeOfHomes.getHome(HomeOfHomes.java:306)
     at
    com.ibm.ejs.container.EJSContainer.getLocalHome(EJSContainer.jav
    a:1212)
     at
    com.ibm.ejs.container.util.LocalInterfaceHomeObjectFactory.getOb
    jectInstance(LocalInterfaceHomeObjectFactory.java:120)
     at
    javax.naming.spi.NamingManager.getObjectInstance(NamingManager.j
    ava:304)
     at
    com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupE
    xt(Helpers.java:896)
     at
    com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectFor
    Lookup(UrlContextHelper.java:191)
     at
    com.ibm.ws.naming.urlbase.UrlContextImpl.processBoundObjectForLo
    okup(UrlContextImpl.java:1775)
     at
    
    
    The only way to recover from this is to restart the application
    server JVM.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V6.1 and V7.0 with applications      *
    *                  containing Container Managed Entity beans.  *
    *                                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Under heavy load, WebSphere             *
    *                      applications containing CMP Entity      *
    *                      beans may experience a deadlock.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In the current design, under heavy load one thread may lock
    the wrapper cache and then attempt to get a lock on the
    J2EEName(or application name in V7) while another thread may
    lock the J2EEName first and then attempt to lock the wrapper
    cache.  This will result in a deadlock.
    

Problem conclusion

  • Changed the EJBContainer code such that the locks are always
    requested in the same order.  This will prevent the deadlock.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.1.0.33 and 7.0.0.13.  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 number

    PM11105

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    61S

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-03-29

  • Closed date

    2010-05-07

  • Last modified date

    2010-05-07

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 6.1

Reference #: PM11105

Modified date: 07 May 2010