IBM Support

PM54417: OOM CAUSED BY EJB CONTAINER CCL LEAK

Fixes are available

8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
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
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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.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
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Customer expereinced java.lang.OutOfMemoryError in native heap.
    CompoundClassLoader leak in EJB Container preventing GC to
    unload the CCL. It had the following reference chain.
    
    There are two issues in EJB Container reported by this APAR
    
    0x023fe6b8 com/ibm/ws/classloader/CompoundClassLoader@21750ab
     0x028b1930 java/security/ProtectionDomain
      0x026f5de0 class com/ibm/websphere/startupservice/EJSRemoteSta
                 telessTestModStartUpHome_6c26d2d3@5063c2
       0x028bed48 com/ibm/ejs/container/BeanMetaData@202b1f2
        0x028be1d0 com/ibm/websphere/startupservice/EJSStatelessTest
                   ModStartUpHomeBean_6c26d2d3
         0x028ba870 com/ibm/ejs/csi/PoolImplThreadSafe@20c70cd
          0x0206f058 [Lcom/ibm/ejs/csi/PoolImplBase;
           0x02061a58 com/ibm/ejs/csi/PoolManagerImpl@4a76b8
    
    0x023fe6b8 com/ibm/ws/classloader/CompoundClassLoader@21750ab
     0x028b1930 java/security/ProtectionDomain
      0x026ff4d0 class com/ibm/websphere/startupservice/_EJSRemoteSt
                 atelessTestModStartUpHome_6c26d2d3_Tie@5079fe
       0x028bd940 com/ibm/websphere/startupservice/_EJSRemoteStatele
                  ssTestModStartUpHome_6c26d2d3_Tie@20c9a4a
        0x02922bb0 com/ibm/rmi/IOR
         0x028c5cc0 com/ibm/CORBA/iiop/ClientDelegate@20c9c4f
          0x028c5df8 com/ibm/websphere/startupservice/_ModStartUpHom
                     e_Stub@20c9b6d
           0x028bd7a8 com/ibm/ws/naming/ipbase/BindingsTableData
            0x028b14c8 java/util/HashMap$Entry
             0x0207c140 [Ljava/util/HashMap$Entry;
              0x0239b280 java/util/HashMap
               0x023937b0 com/ibm/ws/naming/ipbase/NameSpace
                0x0238f988 com/ibm/ws/naming/jcache/Cache
    

Local fix

  • if not restarting application is possible, this may help the
    problem occurs.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V6.1.0 and V8.0                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Application class loaders are not       *
    *                      garbage collected leading to            *
    *                      increased native memory use             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The background thread for managing pools of EJB instances
    retained a reference to the metadata for all EJBs it had
    processed until it woke up to manage pools again.  These
    references prevented application class loaders from being
    garbage collected.
    The startup bean service looked up home stubs using a
    caching-enabled InitialContext associated with the server.
    This cache was never cleared, which prevented application
    class loaders from being garbage collected.
    

Problem conclusion

  • The background thread was modified to promptly clear
    references to EJB metadata after running.  The startup bean
    service was modified to use a caching-disabled InitialContext.
    
    APAR PM54417 is currently targeted for inclusion in Service
    Level (Fix Pack) 6.1.0.43 of WebSphere Application Server V6.1
    and Fix Pack 8.0.0.3 of WebSphere Application Server V8.0.
    
    The fix will also be delivered as sysrouted APAR PM55502 in
    WebSphere Application Server V7.0 Fix Pack 7.0.0.23.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM54417

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-12-14

  • Closed date

    2012-01-06

  • Last modified date

    2012-04-03

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

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

    PM55502

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R610 PSY UK76696

       UP12/03/18 P F203

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Document information

More support for: WebSphere Application Server for z/OS
General

Software version: 6.1

Reference #: PM54417

Modified date: 03 April 2012