PK83186: OutOfMemoryError due to a memory leak when deploying ear that contains an EJB with a message driven bean (MDB).

Fixes are available

APAR status

Closed as program error.

Error description

Problem: There is a memory leak that occurs when deploying
enterprise applications that contain message driven beans (MDBs)
that may result in a java.lang.OutOfMemoryError being recorded
in the SystemOut.log or SystemErr.log file.

--> The problem is when user deploys a message-driven bean.
There are references that are not possible to remove.
OutOfMemory would be produced because there are a lot of
references in the ClassLoader if user want to start and stop the
application running on the appServer.

If user don't deploy an message-driven bean, no references are
in memory.... Just when the enterprise archive file (EAR )
contains a message-driven bean, user have the problem.

A sample heap stack can be seen below:

0x0309ee08 com/ibm/ws/classloader/CompoundClassLoader@5ae75b6d
Reference to application class loader:
0x0a59b3d8 com/ibm/ejs/container/HomeRecord@5809db27
0x0a59b348 java/util/Hashtable$Entry@580d5b27
0x0a4ab358 [Ljava/util/Hashtable$Entry;@400ddb27
0x0a4ab398 java/util/Hashtable@400bdb27
0x0a4ab3f0 com/ibm/ejs/csi/EJBModuleMetaDataImpl@40089b27
0x0a59bb58 com/ibm/ejs/container/BeanMetaData@584ddb27
0x09130948 com/ibm/ejs/container/MDBWrapper@ddd5b3d
0x09130988
com/ibm/ejs/container/EJSWrapperCommon@ddb5b3d
0x0a5ab618 com/ibm/ejs/container/MDBHomeBean@4027db27
0x0a5ac2d0 com/ibm/ejs/csi/PoolImplThreadSafe@43819b27
0x059d0cd8 [Lcom/ibm/ejs/csi/PoolImplBase;@7a29db59
0x059d0d18 com/ibm/ejs/csi/PoolManagerImpl@7a579b59
0x03c2af98
com/ibm/ejs/csi/PoolImplThreadSafe@ebdb6b
0x03c27d60
com/ibm/ejs/container/MDBHomeBean@67c1b6b
0x03c27cf0
com/ibm/ejs/container/CMStatelessBeanO@6709b6b
0x03c93118
com/ibm/ejs/container/HomeRecord@5c1fdb6b

Local fix

None
There is nothing a customer can do without applying a fix to
prevent the memory leak (unless they want to not deploy MDBs).
Stopping and restarting the AppServer after deploying is a
workaround.

Candicate to be fix in next release.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM? WebSphere? Application    *
*                  Server V6.0.2, V6.1.0, V6.1.0 Feature Pack  *
*                  for Enterprise JavaBeans 3.0, and V7.0.0.   *
****************************************************************
* PROBLEM DESCRIPTION: When a user stops their application     *
*                      they may find that the ClassLoader      *
*                      associated with the app continues to    *
*                      reside in memory.                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The Enterprise JavaBeans (EJB) Container is not properly
cleaning up (releasing) its references to the ClassLoaders it
uses when an EJB module is stopped.  As such, the ClassLoader
will continue to reside in memory when the associated
application is stopped.  The ClassLoader will reside in memory
until the Application Service containing it is stopped.

Problem conclusion

With this fix, code will be added to ensure that when an
application is stopped that the EJB Container cleans up
(releases references to) ClassLoaders it uses.

The fix for this APAR is currently targeted for inclusion in
Service Levels (Fix Packs) 6.0.2.37, 6.1.0.27, Enterprise
JavaBeans 3.0 Feature Pack Fix Pack 27 (6.1.0.27), and 7.0.0.5
of WebSphere Application Server versions 6.0.2, 6.1.0, and
7.0.0.

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
PK83186
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
60W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-03-24
Closed date
2009-05-11
Last modified date
2009-08-19

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

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021

Tips

PK83186: OutOfMemoryError due to a memory leak when deploying ear that contains an EJB with a message driven bean (MDB).

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R700 PSY

Document Information

Share your feedback

Need support?