IBM Support

IT07219: WMQ FTE: FTE TRANSFER ENTERS INTO THE RECOVERY STATE WHEN THE SFTP CONNECTION HAS FAILED INSTEAD OF THE FAILED STATE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using a protocol bridge agent to connect to an SFTP file
    server using an incorrect host key for authentication, the
    transfer request enters recovery. The transfer remains in the
    started state and does not either complete as successful or
    complete as a failed transfer.
    

Local fix

  • Correct the file server host key in the protocol bridge agent's
    ProtocolBridgeCredentials.xml file such that it is correct for
    the target file server.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    The issue affects users of:
    
     - WebSphere MQ File Transfer Edition V7.0.4
     - WebSphere MQ Managed File Transfer V7.5
     - IBM MQ Managed File Transfer V8.0
    
    who have a protocol bridge agent that connects to an SFTP file
    server and a Host Key for the SFTP file server has been
    specified in the agent's ProtocolBridgeCredentials.xml file.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When using WebSphere MQ File Transfer Edition (FTE) or Managed
    File Transfer (MFT) protocol bridge agent to connect to an SFTP
    file server, a "hostKey" attribute can be configured on the
    element within the ProtocolBridgeCredentials.xml file for the
    agent that defines the file server host SSH fingerprint. For
    example:
    
    
    
        .... private key ...
    
    
    
    When a host key is specified in the
    ProtocolBridgeCredentials.xml file it is compared to that
    returned from the SFTP file server when a connection is
    established.
    
    If the host key configured in the ProtocolBridgeCredentials.xml
    file did not match that returned by the SFTP file server, then
    the file transfer would enter the "recovery" state and would be
    retried periodically. This resulted in the transfer continually
    entering the recovery state each time it was restarted and a new
    connection to the SFTP file server established, because the
    configured host key did not match that returned by the file
    server. The file transfer would continue to recover and retry
    until a user cancelled the transfer request, e.g., using the
    fteCancelTransfer.
    

Problem conclusion

  • The protocol bridge agent code has been updated such that if the
    host key configured in the ProtocolBridgeCredentials.xml does
    not match that returned by the SFTP file server when connecting,
    the file transfer is failed. When the file transfer is failed in
    this scenario, the corresponding supplement information in the
    transfer log message will contain the reason code and message:
    
    BFGBR0127E: Bridge agent has rejected connection with
    {SFTP_file_server_host_name} as its supplied host key does not
    match the expected value. Host key returned was
    {host_key_value}.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.4.6
    v7.5       7.5.0.6
    v8.0       8.0.0.4
    
    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

    IT07219

  • Reported component name

    WMQ FILE TRANSF

  • Reported component ID

    5724R1000

  • Reported release

    704

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-02-18

  • Closed date

    2015-07-31

  • Last modified date

    2016-05-05

  • 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:
05 May 2016