IBM Support

IT38611: ABEND VALIDATING ELEMENT SUBJECT TO AN IDENTITY CONSTRAINT WHEN THE ELEMENT OR CHILD IS NULL IN THE XMLNSC PARSER

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 an XML message is parsed with validation enabled and an
    element is subject to an identity constraint (e.g. a <xs:unique>
    constraint) and the element itself or one of its children is
    nillable and nil then an abend will occur. The abend stack may
    not resolve correctly, if it does resolve correctly then the
    following stack is expected:
    
    IDCContext_endIDCStateHistoryContext in libBIPNVBRT.so
    Instructions_endIDC in libBIPNVBRT.so
    VMContext_handleEndElementEvent in libBIPNVBRT.so
    VMScannerEventQueue_produceEndElementEvent in libBIPNVBRT.so
    VMScannerEventQueue_scanEndElement in libBIPNVBRT.so
    DocumentEntityScanner_stateUnbufferedEndElement in
    libBIPNVBRT.so
    xlxpc::XLXPCParser::parseAll in libBIPNVBRT.so
    
    An example message that can cause the abend is
    
    <A xmlns="http://www.example.org/Test"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:nil="true" />
    
    when validated against the following schema:
    
    <?xml version="1.0" encoding="UTF-8"?>
    <schema xmlns="http://www.w3.org/2001/XMLSchema"
    targetNamespace="http://www.example.org/Test"
    xmlns:tns="http://www.example.org/Test"
    elementFormDefault="qualified">
    	<element name="A" nillable="true" type="string">
    		<unique name="idx">
    			<selector xpath=".//tns:Id" />
    			<field xpath="tns:IdField"/>
    		</unique>
    	</element>
    </schema>
    

Local fix

  • Disable validation, remove the nil elements, or remove the
    identity constraint.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of the XMLNSC parser in IBM App Connect Enterprise v11
    or v12
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If an XML message is parsed with validation enabled and an
    element is subject to an identity constraint (e.g. a <xs:unique>
    constraint) and the element itself or one of its children is
    nillable and nil then an abend will occur. The abend stack may
    not resolve correctly, if it does resolve correctly then the
    following stack is expected:
    
    IDCContext_endIDCStateHistoryContext in libBIPNVBRT.so
    Instructions_endIDC in libBIPNVBRT.so
    VMContext_handleEndElementEvent in libBIPNVBRT.so
    VMScannerEventQueue_produceEndElementEvent in libBIPNVBRT.so
    VMScannerEventQueue_scanEndElement in libBIPNVBRT.so
    DocumentEntityScanner_stateUnbufferedEndElement in
    libBIPNVBRT.so
    xlxpc::XLXPCParser::parseAll in libBIPNVBRT.so
    
    An example message that can cause the abend is
    
    <A xmlns="http://www.example.org/Test"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:nil="true" />
    
    when validated against the following schema:
    
    <?xml version="1.0" encoding="UTF-8"?>
    <schema xmlns="http://www.w3.org/2001/XMLSchema"
    targetNamespace="http://www.example.org/Test"
    xmlns:tns="http://www.example.org/Test"
    elementFormDefault="qualified">
        <element name="A" nillable="true" type="string">
            <unique name="idx">
                <selector xpath=".//tns:Id" />
                <field xpath="tns:IdField"/>
            </unique>
        </element>
    </schema>
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT38611

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0550

  • Reported release

    B00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-10-06

  • Closed date

    2023-02-06

  • Last modified date

    2023-02-06

  • 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

    APP CONNECT ENT

  • Fixed component ID

    5724J0550

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
13 February 2023