Fixes are available
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.45: Java SDK 1.6 SR16 FP60 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
A spurious exception may be thrown by the WebSphere Application Server XML parser for a well-formed UTF-16 or UTF-32 encoded XML document. Example stack trace: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[-1,-1] Message: An invalid XML character (Unicode: 0x0) was found in the value of attribute "href". StackTrace: ------- com.ibm.xml.xlxp2.api.stax.msg.StAXMessageProvider.throwWrappedX MLStreamException(StAXMessageProvider.java:76), com.ibm.xml.xlxp2.api.stax.XMLStreamReaderImpl.produceFatalError Event(XMLStreamReaderImpl.java:2008), com.ibm.xml.xlxp2.api.jaxb.JAXBXMLStreamReader.produceFatalError Event(JAXBXMLStreamReader.java:356), com.ibm.xml.xlxp2.scan.DocumentScanner.reportFatalError(Document Scanner.java:4871), com.ibm.xml.xlxp2.scan.DocumentScanner.reportFatalError(Document Scanner.java:1212), com.ibm.xml.xlxp2.scan.DocumentScanner.scanRemainingAttValue(Doc umentScanner.java:2543), com.ibm.xml.xlxp2.scan.DocumentScanner.scanNamespaceURI(Document Scanner.java:2435), com.ibm.xml.xlxp2.scan.DocumentScanner.scanNamespaceURI(Document Scanner.java:4373), com.ibm.xml.xlxp2.scan.DocumentScanner.scanSpecifiedAttValue(Doc umentScanner.java:4387), com.ibm.xml.xlxp2.scan.DocumentScanner.scanAttributes(DocumentSc anner.java:2395), com.ibm.xml.xlxp2.scan.DocumentScanner.scanStartElementCommon(Do cumentScanner.java:2292), com.ibm.xml.xlxp2.scan.DocumentScanner.scanStartElement(Document Scanner.java:2253), com.ibm.xml.xlxp2.scan.DocumentScanner.nextEvent(DocumentScanner .java:1301), com.ibm.xml.xlxp2.api.stax.XMLStreamReaderImpl.next(XMLStreamRea derImpl.java:581), com.ibm.xml.xlxp2.api.stax.XMLInputFactoryImpl$XMLStreamReaderPr oxyImpl.next(XMLInputFactoryImpl.java:183), com.ibm.xml.xlxp2.api.wssec.WSSXMLInputFactory$WSSStreamReaderPr oxy.next(WSSXMLInputFactory.java:55) ...
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All IBM WebSphere Application Server users * * of StAX, JAXB and JAX-WS. * **************************************************************** * PROBLEM DESCRIPTION: An XMLStreamException may be thrown * * for a well-formed UTF-16 or UTF-32 * * encoded XML document * **************************************************************** * RECOMMENDATION: Install a fix pack that contains this * * APAR. * **************************************************************** A spurious exception may be thrown by the WebSphere Application Server XML parser for a well-formed UTF-16 or UTF-32 encoded XML document. Example stack trace: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[-1,-1] Message: An invalid XML character (Unicode: 0x0) was found in the value of attribute "href". StackTrace: ------- com.ibm.xml.xlxp2.api.stax.msg.StAXMessageProvider.throwWrappedX MLStreamException(StAXMessageProvider.java:76), com.ibm.xml.xlxp2.api.stax.XMLStreamReaderImpl.produceFatalError Event(XMLStreamReaderImpl.java:2008), com.ibm.xml.xlxp2.api.jaxb.JAXBXMLStreamReader.produceFatalError Event(JAXBXMLStreamReader.java:356), com.ibm.xml.xlxp2.scan.DocumentScanner.reportFatalError(Document Scanner.java:4871), com.ibm.xml.xlxp2.scan.DocumentScanner.reportFatalError(Document Scanner.java:1212), com.ibm.xml.xlxp2.scan.DocumentScanner.scanRemainingAttValue(Doc umentScanner.java:2543), com.ibm.xml.xlxp2.scan.DocumentScanner.scanNamespaceURI(Document Scanner.java:2435), com.ibm.xml.xlxp2.scan.DocumentScanner.scanNamespaceURI(Document Scanner.java:4373), com.ibm.xml.xlxp2.scan.DocumentScanner.scanSpecifiedAttValue(Doc umentScanner.java:4387), com.ibm.xml.xlxp2.scan.DocumentScanner.scanAttributes(DocumentSc anner.java:2395), com.ibm.xml.xlxp2.scan.DocumentScanner.scanStartElementCommon(Do cumentScanner.java:2292), com.ibm.xml.xlxp2.scan.DocumentScanner.scanStartElement(Document Scanner.java:2253), com.ibm.xml.xlxp2.scan.DocumentScanner.nextEvent(DocumentScanner .java:1301), com.ibm.xml.xlxp2.api.stax.XMLStreamReaderImpl.next(XMLStreamRea derImpl.java:581), com.ibm.xml.xlxp2.api.stax.XMLInputFactoryImpl$XMLStreamReaderPr oxyImpl.next(XMLInputFactoryImpl.java:183), com.ibm.xml.xlxp2.api.wssec.WSSXMLInputFactory$WSSStreamReaderPr oxy.next(WSSXMLInputFactory.java:55) ...
Problem conclusion
The XML parser's UTF-16 and UTF-32 decoders occasionally passed the wrong byte array as a parameter to the read method of java.io.InputStream. Data written to this array would be lost and interpreted by the XML parser as being incomplete or malformed. The issue was fixed by ensuring that the correct byte array is always passed as input to the InputStream's read method The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.33 and 8.0.0.9. 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
PI14400
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-03-25
Closed date
2014-04-23
Last modified date
2014-04-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 APP S
Fixed component ID
5724J0800
Applicable component levels
R700 PSY
UP
R800 PSY
UP
Document Information
Modified date:
14 October 2021