IBM Support

PM12587: A JAX-RPC WEB SERVICE IS UNABLE TO PARSE A JMS TEXT MESSAGE THAT CONTAINS DOUBLE BYTE CHARACTERS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A JAX-RPC or Service Component Architecture (SCA) web service
    can receive Java Message Service (JMS) Text messages from
    a JMS transport.  If the inbound text message contains
    characters that are represented by double byte UTF-8
    characters (example is an umlaut), the following error may
    occur:
    
    org.xml.sax.SAXParseException: Invalid byte 2 of 2-byte
    UTF-8 sequence.
    at
    org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseExcepti
    on(Unknown Source)
    at
    org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown
    Source)
    at
    org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
    Source)
    at
    org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
    Source)
    at
    org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentCo
    ntentDispatcher.dispatch(Unknown Source)
    at
    org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocume
    nt(Unknown Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
    Source)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server users of   *
    *                  JAX-RPC or Service Component Architecture   *
    *                  (SCA) with Java Message Service (JMS)       *
    ****************************************************************
    * PROBLEM DESCRIPTION: A SAXParseExcecption may occur when     *
    *                      using JAX-RPC or SCA with JMS messages  *
    ****************************************************************
    * RECOMMENDATION:  Install a fixpack containing this APAR      *
    ****************************************************************
    A JAX-RPC or Service Component Architecture (SCA) web service
    can receive text messages from a JMS transport.  If the
    inbound text message contains characters that are represented
    by double byte UTF-8 characters (example is an umlaut), the
    following error may occur:
    
    org.xml.sax.SAXParseException: Invalid byte 2 of 2-byte
    UTF-8 sequence.
     at
    org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseExcepti
    on(Unknown Source)
     at
    org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown
    Source)
     at
    org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
    Source)
     at
    org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
    Source)
     at
    org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentCo
    ntentDispatcher.dispatch(Unknown Source)
     at
    org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocume
    nt(Unknown Source)
     at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
    Source)
    

Problem conclusion

  • The root of the problem is incorrect translation code in the
    JAX-RPC engine.  The inbound message was not being parsed as a
    UTF-8 byte stream.
    
    The JAX-RPC engine is corrected to obtain the character
    encoding from the incoming message's Content-Type Mime header.
    The JAX-RPC engine reads the message using the obtained
    character encoding.
    
    This same problem is fixed in V6.1 and V7.0 by PK97663.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 6.0.2.43.  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

    PM12587

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    60A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-04-20

  • Closed date

    2010-04-22

  • Last modified date

    2010-04-22

  • APAR is sysrouted FROM one or more of the following:

    PK97663

  • 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

  • R60A PSY

       UP

  • R60H PSY

       UP

  • R60I PSY

       UP

  • R60P PSY

       UP

  • R60S PSY

       UP

  • R60W PSY

       UP

  • R60Z PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022