Fixes are available
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
An OutOfMemory is generated and the heapdump will show that the largest memory user is "com.ibm.xml.xlxp2.jaxb.unmarshal.impl.JAXBDocumentScanner" which contains "com.ibm.xml.xlxp2.scan.util.DataBuffer" objects. The problem does not affect UTF-8 encoding, but affects ASCII and others. The problem occurs when CRLF sequence is split in between two buffers. Smaller buffer sizes (64k default) is likely to increase chances of problem occurring. The issue was identified on WebSpere Application Server Network Deployment edition, V8.5.5 The fix will be included in both V8.5 and V8.0 releases
Local fix
Use UTF-8 instead of ASCII OR If using ASCII increase the buffer size to larger than 64k
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server. The problem does not affect UTF-8 * * encoding, but affects ASCII and others * **************************************************************** * PROBLEM DESCRIPTION: Out of memory error with large number * * of * * com.ibm.xml.xlxp2.scan.util.DataBuffer * * objects using XLXP parser * **************************************************************** * RECOMMENDATION: * **************************************************************** The problem does not affect UTF-8 encoding, but affects ASCII and others. Problem occurs when CRLF line breaks are used in some circumstances.
Problem conclusion
Code was modified to correctly handle CRLF line breaks with ASCII and other encodings. The fix for this APAR is currently targeted for inclusion in fix packs 8.0.0.13 and 8.5.5.10. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
1. Do not use CRLF line endings (convert to LF or CR only) 2. Setting com.ibm.xml.xlxp2.api.util.encoding.DataSourceFactory.bufferLeng to larger number may reduce occurrences of the problem.
Comments
APAR Information
APAR number
PI57463
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-02-17
Closed date
2016-04-11
Last modified date
2016-04-11
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
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022