IBM Support

IT22710: MFT Agent ABENDs with OutOfMemory error when configured with a resource monitor

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

  • A java.lang.OutOfMemory (OOM) error condition was reported by a
    WebSphere MQ File Transfer Edition (FTE) agent configured with a
    resource monitor that had been running for an extended period of
    time.  Javacores generated by the agent JVM when the OOM
    condition occurred indicated an exhaustion of Java heap memory.
     The accompanying Java heapdumps showed the vast majority of the
    memory was consumed by a java.util.HashMap within the
    com.ibm.wmqfte.monitor.task.MonitorTaskStatus class.
    

Local fix

  • Restart agents running resource monitors periodically.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of:
    
      - WebSphere MQ File Transfer Edition
      - WebSphere MQ Managed File Transfer
      - IBM MQ Managed File Transfer
    
    who have configured agents with one or more resource monitors.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When a Managed File Transfer (MFT) resource monitor's trigger
    condition was satisfied and the managed task configured on the
    resource monitor was requested, some information about the task
    was cached by the monitor.  This would then be referred to later
    where the information was published to the SYSTEM.FTE/Monitors
    topic if either:
    
      - the managed task was successfully requested and the
    monitorReportTriggerSatisfied agent property had been set to the
    value true
    
    or
    
       - there was a failure to request the managed task and
    monitorReportTriggerFail agent property had been set to the
    value true.
    
    The cached information about the managed task to request when
    the resource monitor trigger was not removed from the internal
    java.util.HashMap collection.  As such, each time the resource
    monitor trigger, the size of this java.util.HashMap would grow
    and consume more memory.  Once a sufficient number of resource
    monitor triggers had been reached, the agent would run out of
    Java heap memory and the JVM would throw a java.lang.OutOfMemory
    error, causing the agent to ABEND.
    

Problem conclusion

  • The agent code has been updated to ensure that the
    java.util.HashMap within the
    com.ibm.wmqfte.monitor.task.MonitorTaskStatus class, used to
    temporarily cache information about managed tasks being
    requested, is cleaned up appropriately when the cached
    information is no longer required.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.4.7
    v7.5       7.5.0.9
    v8.0       8.0.0.9
    v9.0 CD    9.0.5
    v9.0 LTS   9.0.0.3
    
    The latest available MQ maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT22710

  • Reported component name

    WMQ FILE TRANSF

  • Reported component ID

    5724R1000

  • Reported release

    704

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-10-09

  • Closed date

    2017-11-30

  • Last modified date

    2017-11-30

  • 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

    WMQ FILE TRANSF

  • Fixed component ID

    5724R1000

Applicable component levels

  • R704 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEP7X","label":"WebSphere MQ File Transfer Edition"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.4","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
30 November 2017