PM25457: LEAK IN COM.IBM.WS.ASYNCHBEANS.WORKMANAGERIMPL AND A WAY TO UNREGISTER THIS CLASS WHEN APPLICATION IS STOPPED

6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
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

APAR status

• Closed as program error.

Error description

• cjWorkListenerRunnablePool class
  com.ibm.ws.asynchbeans.WorkManagerImpl @ 0x4391540
  
  
  This APAR is for a leak from the WorkManagerImpl
  ----------------------------------------------------------------
  --------
  ------------------------
  com.ibm.ws.classloader.CompoundClassLoader @ 0x1bb20658
  '- <classloader>, <classLoader> class
  com.ibm.commerce.threadmanagement.internal.BaseWorkListener @
  0x19307c50
  '- <class> com.ibm.commerce.threadmanagement.internal.
  BaseWorkListener@ 0x1bb91560
  '- cjWL com.ibm.ws.asynchbeans.CJWorkListenerRunnable @
  0x6790e50
  '- item java.util.concurrent.ConcurrentLinkedQueue$Node
  @0x28a8d220
  '- tail java.util.concurrent.ConcurrentLinkedQueue @
  0x6790d48
  '- objectList com.ibm.ws.objectpool.FastObjectPoolImpl
  @0x6790d08
  '- pool com.ibm.ws.objectpool.ObjectPoolImpl @
  0x64c7730
  '- cjWorkListenerRunnablePool class com.ibm.ws.
  asynchbeans.WorkManagerImpl @ 0x3cdee10
  '- org.eclipse.osgi.internal.baseadaptor.
  DefaultClassLoader @ 0xfa0dd8
  ----------------------------------------------------------------
  --------
  ------------------------
  WorkManagerImpl maintains a reference to a Commerce class
  (BaseWorkListener which implements commonj.work.WorkListener)
  even after the application from which the class belongs is
  stopped.
  
  This reference is not cleaned update/unregistered during
  application shutdown.
  This problem happened with WebSphere Commerce Server
  applications.
  
  
  The problem is not that the async beans are using too much
  memory.
  The problem is that this code maintain a live reference to an
  application class which prevents the application from being
  properly disposed (Garbage Collected) after it has been stopped.
  
  The AsynchBean code should not keep references to the
  application after the application is stopped. This APAR
  addresses a way to unregister the listener (BaseWorkListener)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V6.1 and V7.0                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: The WorkManagerImpl of AsynchBean is    *
  *                      indirectly causing an OutOfMemory       *
  *                      error under heavy load.                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The WorkManagerImpl is holding a live referecne to an
  application object even after the application is stopped.
  Therefore the application object which is holding onto a major
  chunk of jvm space is not getting Garbage Collected.
  

Problem conclusion

• The problem is fixed after the code is modified such that all
  live references to the application objects are released.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 6.1.0.37 and 7.0.0.17.  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

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP

• R700 PSY

     UP