IBM Support

IT34042: INTEGRATION NODE CRASHES WITH OUTOFMEMORY ERROR FROM NODEJS

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

  • The integration node(bipbroker process) is seen growing memory
    in nodejs heap. The issue is evident when you have several
    integration servers and deployed artifacts and you use IBM
    Tivoli Monitoring agent to monitor the integration node. Once
    the nodejs heap fills up its default 2gb, you will see the
    integration node crash with an abend file. The following calls
    are seen in the abend
    stack
    
    v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char
    const*, bool) from
    v8::internal::V8::FatalProcessOutOfMemory(v8:
    :internal::Isolate*, char const*, bool)
    f
    v8::internal::Heap::PerformGarbageCollection
    
    The reason for
    the leak is internal issues to the nodejs runtime where it
    fails to garbage collect certain objects created by the ACE
    code.
    
    A user can take nodejs heap snapshot of bipbroker
    process at regular intervals and compare their sizes to see if
    the growth is present.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM App Connect Enterprise V11 using monitoring
    tools, such as IBM Tivoli Monitoring.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When using a monitoring tool such as IBM Tivoli Monitoring to
    monitor the status of an integration node with several
    integration servers and deployed artifacts, the memory heap used
    by the Node.js runtime engine increases over time. Once the
    Node.js heap exhausts its default 2GB limit, the integration
    node terminates with an abend file. The following calls are seen
    in the abend stack:
    
    v8::Utils::ReportOOMFailure
    v8::internal::V8::FatalProcessOutOfMemory
    v8::internal::Heap::PerformGarbageCollection
    
    The reason for the leak is an internal issue with the Node.js
    runtime engine where it fails to garbage collect certain objects
    created by the integration node.
    
    A user can take a Node.js heap snapshot of the bipbroker process
    at regular intervals and compare their sizes to see if the
    growth is occurring.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT34042

  • 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

    2020-08-28

  • Closed date

    2020-12-15

  • Last modified date

    2020-12-15

  • 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

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00"}]

Document Information

Modified date:
16 December 2020