IBM Support

IT11150: WMQ MFT 7.5 PBA INCORRECTLY MARKS THE TRANSFER AS FAILED WHEN A FTP STORE REQUEST TIMES OUT WITH FTP REPLY CODE 425.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • While MQ MFT is sending a managed file transfer to a remote FTP
    server the FTP server returns an FTP Reply Code 425 - "Can't
    open data connection". The MFT protocol Bridge Agent attempts
    the STOR command again but but if both attempts fail it throws
    an IOException containing the string: "Accept timed out" and
    incorrectly marks the managed transfer as "Failed".
    
    The FTP reply 425 is a transient error so the correct behaviour
    would be to treat this condition as recoverable, and put the
    managed transfer into recovery so that it is re-queued it for
    processing at later time.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of WebSphere MQ Managed File Transfer
    v7.5 and V8 Protocol Bridge Agent who are communicating with an
    FTP(S) Server which fails to process a write request due to
    resource limitations.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    While MQ MFT is processing a file transfer request to a remote
    FTP(S) server it sends FTP STOR requests to write data to the
    remote file. If the FTP server cannot process the request and
    times out it returns FTP Reply Code 425 "Can't open data
    connection". The MFT protocol Bridge Agent attempts the STOR
    command twice but if both attempts fail it throws an IOException
    containing the string: "Accept timed out" and marks the managed
    transfer as "Failed".
    
    The Reply Code 425 is a transient error opening the data
    connection caused by a resource shortage so the correct
    behaviour would be to treat this condition as recoverable, and
    put the managed transfer into recovery.
    

Problem conclusion

  • The protocol bridge agent has been updated to handle the dropped
    connection / rejected request as a recoverable error and the
    file transfer is put into RECOVERY status so that it can be
    retried.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.5       7.5.0.6
    v8.0       8.0.0.5
    
    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

    IT11150

  • Reported component name

    WMQ MFT

  • Reported component ID

    5724H7242

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-09-10

  • Closed date

    2015-10-30

  • Last modified date

    2015-10-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 MFT

  • Fixed component ID

    5724H7242

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSCUHLE","label":"WMQ Managed File Transfer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
30 October 2015