IBM Support

IT38542: Transfer request that hit a problem may see increase in Memory or OutOfMemory Exception

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

  • IBM MQ MFT V9.2.x failed transfer request causes consuming
    memory, which can result over time an OutOfMemory and heap dump
    being generate for MFT agents.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of IBM MQ Managed File Transfer
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When a transfer request is submitted to the source agent it will
    look to create a state object for the request and place it onto
    the queuedTransfersList in order to be processed.  The agent
    will then look to get the transfer from queuedTransfersList and
    look to process it, and will move it onto the
    activeTransfersList.  If transfer request hits a problem,
    waiting for destination agent capacity or waiting for the
    destination agent to respond with a resync response the transfer
    will be placed on to the inactiveTransfersList &
    inactiveTransfersListForRT.
    
    The agent will look to check for inactive transfer attempt to
    restart the transfer request and will look to remove it from the
    inactiveTransfersList and place it on the activeTransfersList.
     However when it does this it does not remove it from the
    inactiveTransfersListForRT.  This leads to an increase in java
    heap memory and the inactiveTransfersListForRT object growing in
    size.
    

Problem conclusion

  • IBM MQ Managed File Transfer has been changed to ensure that we
    release the objects correctly when they are no longer in the
    inactive transfer state.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.5
    v9.x CD    9.2.5
    
    The latest available 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

    IT38542

  • Reported component name

    MQ BASE V9.2

  • Reported component ID

    5724H7281

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-09-29

  • Closed date

    2021-11-16

  • Last modified date

    2021-11-16

  • 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

    MQ BASE V9.2

  • Fixed component ID

    5724H7281

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"920"}]

Document Information

Modified date:
17 November 2021