IBM Support

PI37349: CONTENT IN XML ELEMENTS SOMETIMES LOST WHEN USING JAX-RPC WEBSERVICES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Sometimes (it depends on the set of data) the data within XML
    content is lost and the SOAP message has incomplete data
    length which is passed to JAX-RPC WebService engine. This
    happens only with SAX/JAX-RPC.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server v8.0 and v8.5                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Content in XML elements lost when       *
    *                      using JAX-RPC webservices.              *
    ****************************************************************
    * RECOMMENDATION:  Install a fix pack that contains this       *
    *                  APAR.                                       *
    ****************************************************************
    When the SAX parser is processing an XML document, data within
    the XML content is lost and the corresponding SOAP message has
    the possiblity of having incomplete data length. This
    incomplete SOAP message is then passed to the JAX-RPC
    WebService engine, which can throw faulty exceptions during
    engine processing.
    

Problem conclusion

  • The XML parser tries to split large chunks of character data
    into multiple character events. If it is the case where we
    have more than 2 data buffers to process, there is a
    particular case where if data spans into another buffer
    (particularly the last buffer), we are prone to miss
    processing the latter half of the last buffer.
    
    The issue was fixed by ensuring that all edge cases related to
    processing the entirety of spanning multiple buffers are
    covered and not missed. This fix was tested in full to ensure
    all edge cases were met.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.11 and 8.5.5.7.  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

    PI37349

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-03-19

  • Closed date

    2015-05-26

  • Last modified date

    2015-05-26

  • 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

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

Document Information

Modified date:
11 January 2022