IBM Support

PM66572: XCIDYNAMICERROREXCEPTION PARSING ERROR FOR LARGE XML INPUT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A parsing error may occur for particular XML inputs larger
    than 64K if the end element tag for the parent of a skipped
    subtree is split across input buffers. This is a rare condition
    that will occur only for certain input data when using lazy
    parsing mode in products such as WebSphere Process Server.
    
    When this occurs, an exception such as the following
    will be thrown:
    
    com.ibm.xml.xci.errors.XCIDynamicErrorException:
    The content of elements must consist of well-formed
    character data or markup.
     at com.ibm.xml.xci.adapters.xlxp.scanner.XCIScanner
         .produceFatalErrorEvent(XCIScanner.java:636)
     at com.ibm.xml.xlxp.internal.s1.scan.DocumentScanner
         .reportFatalError(DocumentScanner.java:4980)
     at com.ibm.xml.xlxp.internal.s1.scan.DocumentScanner
         .reportFatalError(DocumentScanner.java:1333)
     at com.ibm.xml.xlxp.internal.s1.scan.DocumentScanner
         .scanMarkup(DocumentScanner.java:2294)
     at com.ibm.xml.xlxp.internal.s1.scan.DocumentScanner
         .nextEvent(DocumentScanner.java:1464)
     at com.ibm.xml.xci.adapters.xlxp.scanner.XCIScanner
         .toNextElementNode(XCIScanner.java:868)
     at com.ibm.xml.xci.adapters.xlxp.scanner
         .DelegatingSubtreeScanner.toNextElementNode
         (DelegatingSubtreeScanner.java:258)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    *                  V8 and V8.5                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Error occurs for rare scenarios         *
    *                      involving                               *
    *                      skipped subtree content that is split   *
    *                      across buffer boundaries.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The issue occurs in skipped subtrees where the end tag of the
    parent element (which owns the skipped content) is split across
    buffer boundaries.   More specifically, it occurs when the '<'
    character of the end tag is the last character in one buffer,
    and the '/' character of the end tag is the first character of
    the next buffer.
    

Problem conclusion

  • The algorithm for processing split skipped subtree content has
    been corrected to properly handle these edge cases.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.5 and 8.5.0.1.  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

    PM66572

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-12

  • Closed date

    2012-08-21

  • Last modified date

    2012-08-21

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

    PM66374

  • 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

  • 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:
29 October 2021