IBM Support

IT25470: FILEOUTPUT NODE LEAKS NATIVE MEMORY VIA JAVA

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 a FileOutput node is used, small Java objects are
    allocated which own references to large natively allocated
    objects. Since these Java objects are small they are
    infrequently garbage collected which results in the large
    native objects persisting for long durations. Under load this
    can appear as a steadily growing memory usage which sometimes
    decreases once a JVM GC is triggered. The Java heap size does
    not grow discernibly during this leak.
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus v10 and IBM App Connect
    Enterprise v11 who use the FileOutput node.		
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The FileOutput node can leak memory associated with XPath
    expressions, this can lead to unexpected process growth in the
    DataFlowEngine or IntegrationServer processes.
    
    The FileOutput node, which is implemented in Java, allocates a
    large chunk of a native memory via a small Java object to handle
    parsing XPath attributes on the node each time a file is sent.
    When the data is sent it is left to the Java GC to clean up
    these objects. Since the Java object is a thin wrapper the JVM
    thinks the memory used by it is small and may delay freeing it
    which can lead to a buildup of large native memory being wasted
    waiting for the JVM to clean up the thin wrappers.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT25470

  • 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-06-22

  • Closed date

    2018-09-26

  • Last modified date

    2018-09-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

    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:
26 September 2018