Fixes are available
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
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
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
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
Excessive memory usage by the IBM StAX implementation may result in a java.lang.OutOfMemoryError. The size of the cached XMLStreamReader objects may grow without bound. Here is a sample heapdump that was collected during a stress test: 1,934,853,366 (94%) [80] 4 array of [Lcom/ibm/xml/xlxp2/api/util/Pool$Poolable; 0xfffffffeb1dfa6d8 531,437,140 (25%) [796] 50 com/ibm/xml/xlxp2/api/wssec/WSSXMLStreamReader 0xfffffffeb1e56ae8 512,072,055 (24%) [796] 47 com/ibm/xml/xlxp2/api/wssec/WSSXMLStreamReader 0xfffffffeb1dfa740 474,720,178 (23%) [796] 50 com/ibm/xml/xlxp2/api/wssec/WSSXMLStreamReader 0xfffffffeb1e217d8 416,623,913 (20%) [796] 51 com/ibm/xml/xlxp2/api/wssec/WSSXMLStreamReader 0xffffffff115d78e0
Local fix
na
Problem summary
**************************************************************** * USERS AFFECTED: All IBM WebSphere Application Server V7.0 * * and V8.0 users of StAX, JAXB and JAX-WS. * **************************************************************** * PROBLEM DESCRIPTION: Excessive memory usage by the IBM * * StAX implementation may lead to an * * OutOfMemoryError. * **************************************************************** * RECOMMENDATION: Install a fix pack that contains this * * APAR. * **************************************************************** When running a JAX-WS application, a tremendous growth in the size of cached XMLStreamReader objects in the heap may be observed. A heapdump collected from a stress test may look like the following: 1,934,853,366 (94%) [80] 4 array of [Lcom/ibm/xml/xlxp2/api/util/Pool$Poolable; 0xfffffffeb1dfa6d8 531,437,140 (25%) [796] 50 com/ibm/xml/xlxp2/api/wssec/WSSXMLStreamReader 0xfffffffeb1e56ae8 512,072,055 (24%) [796] 47 com/ibm/xml/xlxp2/api/wssec/WSSXMLStreamReader 0xfffffffeb1dfa740 474,720,178 (23%) [796] 50 com/ibm/xml/xlxp2/api/wssec/WSSXMLStreamReader 0xfffffffeb1e217d8 416,623,913 (20%) [796] 51 com/ibm/xml/xlxp2/api/wssec/WSSXMLStreamReader 0xffffffff115d78e0
Problem conclusion
For efficiency the IBM StAX implementation caches XMLStreamReader objects in a pool for reuse. This pool may retain strong references to XMLStreamReaders which continue to grow over time, eventually resulting in an OutOfMemoryError if an excessive amount of memory is used by those objects. A system property called com.ibm.xml.xlxp2.api.util.Pool.STRONG_REFERENCE_POOL_MAXIMUM_SI ZE is provided by this APAR. Its value is an integer and when set, it limits the number of XMLStreamReaders (and XMLStreamWriters) that will be cached using strong references. To avoid the OutOfMemoryError, set the system property to 0. This will force all XMLStreamReaders to be cached using SoftReferences, allowing the garbage collector to reclaim the memory they occupy in the cache at any time. When the system property is not set its default value is 10. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.21 and 8.0.0.2. 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
PM42465
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-06-27
Closed date
2011-09-14
Last modified date
2011-09-14
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
R700 PSY
UP
R800 PSY
UP
Document Information
Modified date:
27 October 2021