IBM Support

IT23305: MQ MFT agent is generating multiple scheduled file transfer instances when its workload is high

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 using scheduled transfers to move files frequently, for
    example every minute, and the workload of the source agent for
    the scheduled transfer is high, multiple instances of a
    scheduled transfer could be submitted to the agent before
    previous instances complete.  This could result in multiple
    transfers attempting to move the same files with all but the
    first instance failing with the error :
    
    BFGIO0110E: File "/directory/filename" does not exist.
    

Local fix

  • Increasing the time between scheduled transfer instances can
    help mitigate against this problem.  For example, changing
    scheduled transfers that are configured to run every minute to
    every ten minutes.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of IBM MQ Managed File Transfer who are
    using scheduled transfers to move large number of files
    frequently.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When an IBM Managed File Transfer (MFT) agent's workload is
    high, it will have to process many messages from its
    SYSTEM.FTE.COMMAND queue.  This can lead to a build up of
    messages on the queue that include new external transfer
    requests, instances of requested scheduled transfers, ping
    requests and transfer recovery commands and cause a small delay
    in the processing of those requests.
    
    With this in mind, consider the scenario of a scheduled transfer
    with a short repeat interval of thirty seconds.
    
    The first time the scheduled transfer was due, a transfer
    request message was submitted to the agent's SYSTEM.FTE.COMMAND
    for asynchronous processing. If the agent did not get round to
    processing this new scheduled transfer request message within
    thirty seconds and registering the scheduled transfer as active
    within its internal state, then another instance of the
    scheduled transfer would be requested, despite the pending first
    instance.
    
    This resulted in two instances of transfer requests for the same
    scheduled transfer present on the agent's SYSTEM.FTE.COMMAND
    queue.  If the scheduled transfer requested source files to be
    deleted at the end of the transfer then only the first processed
    transfer would succeed as the source file would be deleted,
    causing the second to fail.
    

Problem conclusion

  • The product code for MQ Managed File Transfer (MFT) has been
    updated such that the scheduler code, which determines whether a
    new instance of a schedule transfer needs to be requested, not
    only checks if the previous transfer is running but also checks
    if one is still pending and waiting to be processed by the
    agent.  This is achieved via the use of an in-memory data
    structure to store the list of pending, but not yet started,
    scheduled transfer instances submitted to the agent's
    SYSTEM.FTE.COMMAND queue.  Note that this in-memory data
    structure is not persisted across agent JVM restarts or recovery
    processing (for example when the agent loses connection to its
    queue manager).
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.9
    v9.0 CD    9.0.5
    v9.0 LTS   9.0.0.4
    
    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

    IT23305

  • Reported component name

    IBM MQ MFT V8.0

  • Reported component ID

    5724H7252

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-12-12

  • Closed date

    2018-02-08

  • Last modified date

    2018-02-08

  • 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

    IBM MQ MFT V8.0

  • Fixed component ID

    5724H7252

Applicable component levels

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

Document Information

Modified date:
08 February 2018