IBM Support

PI14400: XMLSTREAMEXCEPTION MAY BE THROWN FOR A WELL-FORMED UTF-16 OR UTF-32 ENCODED XML DOCUMENT

Subscribe

You can track all active APARs for this component.

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

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PI14400

Modified date: 23 April 2014