IBM Support

IT05583: WEBSPHERE MQ MANAGED FILE TRANSFERS REMAIN IN RECOVERY AND DO NOT COMPLETE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A file transfer that is performed by WebSphere MQ Managed File
    Transfer does not report a transfer as completed, despite the
    file existing correctly at the destination. When viewing the
    transfer in the "Transfer Log" page of the WebSphere MQ Explorer
    Managed File Transfer plug-in, only the "started" transfer log
    message is reported and the "Completion State" of the transfer
    is reported as "Recovering". The transfer does not recover and
    the source agent for the transfer does not publish the transfer
    log "progress" or "completed" messages, as would be expected.
    

Local fix

  • Restart the WebSphere MQ Managed File Transfer destination agent
    for the transfer.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects all users of WebSphere MQ Managed File
    Transfer.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When performing a transfer using WebSphere MQ Managed File
    Transfer, the destination agent for a transfer acknowledges data
    it has received and written to the destination file at
    negotiated intervals. The amount of time the source agent waits
    for these acknowledgement messages are determined by the agent
    properties listed below. The default values are given in
    brackets.
    
      - transferAckTimeout (60 000)
    
    and
    
      - transferAckTimeoutRetries (5)
    
    The transferAckTimeout property is specified in milliseconds.
    Therefore, by default, the source agent will wait up to five
    minutes for an acknowledgement message. Should this timeout
    expire, then the source agent puts the transfer into recovery
    and sends a "resynchronise" message to the destination agent.
    
    Once all the data had been acknowledged by the destination agent
    and the final processing for the transfer had completes, the
    destination agent then send a "completed" message to the source
    agent.
    
    
    If the destination agent received and processed a resynchronise
    message after sending the final acknowledgement message to the
    source agent but before the completed message, then the
    destination agent would erroneously consider the transfer
    complete, rather than attempt to recover it. As a result, the
    destination agent would not respond to the resynchronise message
    sent by the source agent and neither would it send the completed
    message. When this occurred, the transfer would remain in
    recovering state at the source agent and the "progress" and
    "completed" transfer log messages would not be published by the
    source agent.
    
    To resolve the situation, such that the transfer could be
    recovered, the destination agent required restarting.
    

Problem conclusion

  • The WebSphere MQ Managed File Transfer Edition agent code has
    been updated such that a destination transfer is only considered
    completed once the "complete" message has been sent to the
    source agent for the transfer.
    
    Therefore, should a destination agent process a resynchronise
    message after all of the data has been acknowledged but before
    the completion message is sent, then the destination agent would
    recover the transfer and send the completion message once the
    recovery has been completed.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.5       7.5.0.5
    v8.0       8.0.0.2
    
    The latest available FTE maintenance can be obtained from
    'Fix List for WebSphere MQ File Transfer Edition 7.0'
    http://www-01.ibm.com/support/docview.wss?uid=swg27015313
    
    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

    IT05583

  • Reported component name

    WMQ MFT

  • Reported component ID

    5724H7242

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-11-14

  • Closed date

    2014-12-04

  • Last modified date

    2015-11-18

  • 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 MFT

  • Fixed component ID

    5724H7242

Applicable component levels

  • R750 PSY

       UP

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5"}]

Document Information

Modified date:
24 September 2021