PK98076: EJB CONTAINER LARGE TRANSACTIONS NOT GARBAGE COLLECTED, CAN CAUSE OUT OF MEMORY

Fixes are available

APAR status

Closed as program error.

Error description

Large transactions with very large number of entity beans are
closed after commit. The problem is, the heap is not freed
after the commit. Eventually, the memory is exausted resulting
in Out Of Memory Exception.

In addition, FFDC creation during large or long-running
transactions could result in Out Of Memory exceptions such as:

Caused by: java.lang.OutOfMemoryError
 at java.lang.StringBuffer.append(StringBuffer.java(Compiled
Code))
 at
com.ibm.ejs.container.ContainerTx.ffdcDump(ContainerTx.java(Comp
iled Code))
 at
com.ibm.ejs.container.EJBContainerDiagnosticModule.ffdcDumpDefau
ltContainerTx(EJBContainerDiagnosticModule.java:494)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server running applications containing      *
*                  large or long-running transactions.         *
****************************************************************
* PROBLEM DESCRIPTION: Users can experience Out Of Memory      *
*                      exceptions running applications         *
*                      containing large or long-running        *
*                      transactions.                           *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This APAR addresses OutOfMemory issues related to large or
long-running transactions, especially those containing large
numbers of entity beans. In rare cases you could possibly see
the following exception in your SystemErr.log indicating a
problem in FFDC within the EJBContainer:

Caused by: java.lang.OutOfMemoryError at
java.lang.StringBuffer.append(StringBuffer.java(Compiled
Code))
 at
com.ibm.ejs.container.ContainerTx.ffdcDump(ContainerTx.java(Comp
iled Code))
 at
com.ibm.ejs.container.EJBContainerDiagnosticModule.ffdcDumpDefau
ltContainerTx(EJBContainerDiagnosticModule.java:494)

Problem conclusion

The fix for 6.0.2.41 includes a back-port of changes in 6.1
that modify the EJBContainer eviction strategy code so that it
will not hold references to evicted objects until the next
eviction cycle, allowing the objects to be cleaned up. This
fix also includes a change to all active WebSphere Application
Server releases to change the EJBContainer FFDC processing to
write information out directly rather than building large
string buffers that could exhaust memory.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.11, 6.1.0.31, 6.0.2.41 .  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
PK98076
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
60A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-10-07
Closed date
2010-01-26
Last modified date
2010-01-26

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
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z 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:
29 December 2021

Tips

PK98076: EJB CONTAINER LARGE TRANSACTIONS NOT GARBAGE COLLECTED, CAN CAUSE OUT OF MEMORY

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

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?