IBM Support

IT15372: MEMORY LEAK IN XML4C WHEN USING ITX/WTX NODES

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

  • When using ITX/WTX nodes in an IIB flow the ITX/WTX libraries
    use the version of XML4C shipped with IIB. The WTX/ITX team has
    identified a memory leak which is resolved under ITX/WTX APAR
    PI62025. The IIB copy of the XML4C libraries also needs to be
    updated to contain this defect fix.
    
    The issue occurs when validating an element in a WTX/ITX node
    where the element has minOccurs=0 and maxOccurs equal to any
    value other than 0 or 1 and when this element is of type "Leaf".
    The symptom is a 200 byte leak per element of this type
    processed.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus version 10 or App Connect
    Enterprise version 11 using the ITX/WTX Nodes.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    <span style="background-color:rgb(255, 255, 255)">When using
    ITX/WTX nodes in an IIB flow the ITX/WTX libraries </span><span
    style="background-color:rgb(255, 255, 255)">use the version of
    XML4C shipped with IIB. The WTX/ITX team has </span><span
    style="background-color:rgb(255, 255, 255)">identified a memory
    leak which is resolved under ITX/WTX APAR </span><span
    style="background-color:rgb(255, 255, 255)">PI62025. The IIB
    copy of the XML4C libraries also needs to be </span><span
    style="background-color:rgb(255, 255, 255)">updated to contain
    this defect fix.                           </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span>
    <span style="background-color:rgb(255, 255, 255)">The issue
    occurs when validating an element in a WTX/ITX node </span><span
    style="background-color:rgb(255, 255, 255)">where the element
    has minOccurs=0 and maxOccurs equal to any  </span><span
    style="background-color:rgb(255, 255, 255)">value other than 0
    or 1 and when this element is of type "Leaf". </span><span
    style="background-color:rgb(255, 255, 255)">The symptom is a 200
    byte leak per element of this type </span><span
    style="background-color:rgb(255, 255, 255)">processed.
                                                       </span>
    
    There are a number of resource name changes between WebSphere
    Message Broker and IBM Integration Bus Version 9.0.  For details
    visit
    http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
    tools.mft.doc/bb23814_.htm
    

Problem conclusion

  • The version of xml4c that is shipped with the product has been
    updated so that it contains the same code change as that made
    for ITX/WTX APAR PI62025
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.20
    v11.0      11.0.0.8
    
    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

    IT15372

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0530

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-05-31

  • Closed date

    2020-03-27

  • Last modified date

    2020-03-27

  • 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

    5724J0530

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":"9.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
27 March 2020