Fixes are available
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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
While the XML parser is handling data via the multiple buffers in which it stores, a java.lang.ArrayIndexOutOfBoundsException may be thrown due to an illegal access of a byte array data structure. The top of the exceptoin stack will look like this: java.lang.ArrayIndexOutOfBoundsException at com.ibm.xml.xlxp2.api.util.DataBufferHelper.computeCoords10(Data BufferHelper.java:116) at com.ibm.xml.xlxp2.api.util.encoding.ByteStreamDataSource.load(By teStreamDataSource.java:218) at com.ibm.xml.xlxp2.scan.util.ParsedEntity.loadMore(ParsedEntity.j ava:230) at com.ibm.xml.xlxp2.scan.util.ParsedEntity.skipBytesUsingMap(Parse dEntity.java:997) at com.ibm.xml.xlxp2.scan.DocumentScanner.scanRemainingAttValue(Doc umentScanner.java:2443) ... This is similar to PI16073 except this issue occurs in the standalone XML parser versus in the feature pack parser.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.5. * **************************************************************** * PROBLEM DESCRIPTION: ArrayIndexOutOfBoundsException may be * * thrown by * * com.ibm.xml.xlxp2.api.util.DataBufferHe * * lper.computeCoords10 * **************************************************************** * RECOMMENDATION: Install a fix pack that contains this * * APAR. * **************************************************************** A DataBufferHelper utility is used for handling line numbers for parser related errors. An ArrayIndexOutOfBoundsException may be thrown due to the handing of an edge case of the particular data structure. The top of the exceptoin stack will look like this: java.lang.ArrayIndexOutOfBoundsException at com.ibm.xml.xlxp2.api.util.DataBufferHelper.computeCoords10(Data BufferHelper.java:116) at com.ibm.xml.xlxp2.api.util.encoding.ByteStreamDataSource.load(By teStreamDataSource.java:218) at com.ibm.xml.xlxp2.scan.util.ParsedEntity.loadMore(ParsedEntity.j ava:230) at com.ibm.xml.xlxp2.scan.util.ParsedEntity.skipBytesUsingMap(Parse dEntity.java:997) at com.ibm.xml.xlxp2.scan.DocumentScanner.scanRemainingAttValue(Doc umentScanner.java:2443)
Problem conclusion
The ArrayIndexOutOfBoundsException is apparent in the utility class DataBufferHelper. There is no check for the edge case of when the end position of an offset is less than the start position of an offset. The solution implies ensuring that this condition is met before processing contents of the byte array. E.g. endOfOffset = -1 and startOfOffset = 0. This would imply to reference array[-1], which is the cause of an ArrayIndextOutOfBoundsException. The fix for this APAR is currently targeted for inclusion in Fix Pack 8.5.5.7 of WebSphere Application Server V8.5. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 In addition, please refer to URL: http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack PTF information.
Temporary fix
Comments
APAR Information
APAR number
PI32805
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-01-15
Closed date
2015-05-20
Last modified date
2015-06-23
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 FOR Z
Fixed component ID
5655I3500
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
28 April 2022