IT34978: Managed transfers get stuck if they are unable to connect to a file server using the SFTP protocol.

APAR status

• Closed as program error.

Error description

• An IBM MQ Managed File Transfer protocol bridge agent is
  configured to connect to a file server using the SFTP protocol.
  When the protocol bridge agent processes a managed transfer
  request involving this file server, the managed transfer get
  stuck and no errors are reported in the protocol bridge agent's
  event log (output0.log).
  
  A trace collected at the time of the issue shows that the
  protocol bridge agent reports the following error at regular
  intervals:
  
  static c.i.w.b.session.sftp.SFTPConnection ----+----+----+----+
   !  openSession, BFGBR0102E: Bridge agent could not locate and
  connect to protocol file server <file_server>
  [com.ibm.wmqfte.bridge.protocol.ProtocolException]
  

Local fix

• Look to make sure the sftp server can be resolved and then look
  to restart the MFT Bridge Agent.  If this does not work may need
  to run fteCleanAgent.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This affects users of IBM MQ Managed File Transfer protocol
  bridge agents (PBAs) that connect to file servers using the SFTP
  protocol.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The IBM MQ Managed File Transfer configuration file
  ProtocolBridgeProperties.xml contains the definitions of file
  servers that a protocol bridge agent can connect to. When a
  protocol bridge agent receives a managed transfer request to
  transfer files either to or from a file server, it will look up
  the definition of that file server in its
  ProtocolBridgeProperties.xml file and use the information to
  connect to it.
  
  If a protocol bridge agent:
  
  - Had been configured to connect to a file server using the SFTP
  protocol.
  - And was unable to resolve the IP address of the file server
  when it attempted to connect to it while processing a managed
  transfer.
  
  then the protocol bridge agent would go into a loop, continually
  trying to reconnect and failing. As a result, the managed
  transfer got stuck and could not proceed.
  
  When this happened, neither the source or destination agents for
  the managed transfer would write any errors or messages about
  that managed transfer to their event log (output0.log).
  
  A trace from the protocol bridge agent at the time when the
  issue occurred contained the following trace point:
  
  c.i.w.b.session.sftp.SFTPConnection         ----+----+----+----+
   !  openSession, BFGBR0102E: Bridge agent could not locate and
  connect to protocol file server <file_server>
  [com.ibm.wmqfte.bridge.protocol.ProtocolException]
  

Problem conclusion

• In order to resolve this issue, IBM MQ Managed File Transfer
  protocol bridge agents have been modified so that if an attempt
  to connect to a file server using the SFTP protocol fails
  because the IP address of the file server could not be resolved,
  then the managed transfer will be marked as "Failed" with the
  following supplementary information:
  
  BFGBR0102E: Bridge agent could not locate and connect to
  protocol file server <file_server>"
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.1 LTS   9.1.0.8
  v9.2 LTS   9.2.0.2
  v9.x CD    9.2.2
  
  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 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 BASE MP

• Fixed component ID

  5724H7271

Applicable component levels