IBM Support

IT23765: ABEND AFTER XMLNSC VALIDATION EXCEPTIONS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • If a message flow uses the Validation Node to perform content
    and value validation on a message in the SOAP or XMLNSC domains
    with the Failure Action node property set to 'Exception', the
    integration server may randomly abend. The abend call stacks
    are inconsistent, but the following stack might be seen if the
    abend occurred when stopping the message flow:
    
    cfree from /lib64/libc.so.6
    ImbXMLNSCServices::ImbXMLNSCServices()
    ImbXMLNSCServices::ImbXMLNSCServices()
    ImbXMLNSCDocHandler::deleteXLXPParser()
    ImbXMLNSCDocHandler::ImbXMLNSCDocHandler()
    ImbXMLNSCNullDocHandler::ImbXMLNSCNullDocHandler()
    ImbXMLNSCParser::ImbXMLNSCParser()
    ImbXMLNSCParser::ImbXMLNSCParser()
    ImbParserManager::deleteParser(ImbParser*)
    ImbMessageGroup::ImbMessageGroup()
    
    Additional Symptom(s) Search Keyword(s):
    

Local fix

  • 1) Use a Failure action of 'ExceptionList' instead of 'Exception
    or
    2) Export environment variable MQSI_FREE_MASTER_PARSERS=YES
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus v10 and IBM App Connect
    Enterprise v11 using the XMLNSC parser with validation.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If a message flow uses the Validation Node to perform content
    and value validation on a message in the SOAP or XMLNSC domains
    with the Failure Action node property set to 'Exception', the
    integration server might randomly abend.
    The abend call stacks are inconsistent, but the following stack
    might be seen if the abend occurs when stopping the message
    flow:
    
    cfree from /lib64/libc.so.6
    ImbXMLNSCServices::ImbXMLNSCServices()
    ImbXMLNSCServices::ImbXMLNSCServices()
    ImbXMLNSCDocHandler::deleteXLXPParser()
    ImbXMLNSCDocHandler::ImbXMLNSCDocHandler()
    ImbXMLNSCNullDocHandler::ImbXMLNSCNullDocHandler()
    ImbXMLNSCParser::ImbXMLNSCParser()
    ImbXMLNSCParser::ImbXMLNSCParser()
    ImbParserManager::deleteParser(ImbParser*)
    ImbMessageGroup::ImbMessageGroup()
    
    An index value into an array of nested elements is not being
    reset following a validation failure that causes the parse to
    stop. After a number of validation failures the index value
    exceeds the array size leading to heap corruption.
    If the Failure Action node property is set to 'ExceptionList
    instead of ''Exception' the parse continues to validate the
    complete document even if validation problems are found. When
    the document has been fully parsed, the nested element index
    pointer will have returned to zero.
    

Problem conclusion

  • The product now resets the element stack array index to 0 (top
    of stack) when reset() is called on the XLXPC parser, preventing
    the abend.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.15
    v11.0      11.0.0.3
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT23765

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-01-18

  • Closed date

    2019-02-25

  • Last modified date

    2019-02-25

  • 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

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
25 February 2019