IT07569: WMQ V7.5 MANAGED FILE TRANSFER PROTOCOL BRIDGE AGENT FAILED TO RECOVER FILE TRANSFER, FDC WITH METHOD "PROCESSRECOVERYMESSAGE"

WebSphere MQ File Transfer Edition V7.0 Fix Pack 7.0.4.6

APAR status

• Closed as program error.

Error description

• A WebSphere MQ Managed File Transfer protocol bridge agent
  generates FFDC files with the following information:
  
  Filename:
  /var/mqm/mqft/logs/MFT/agents/AGENT/logs/ffdc/FFDC.FTE.201505131
  64338862.1091350785738471393.log
  Level: f750-FP-20130619-1001
  Time: 13/05/2015 16:43:38:862 GMT
  Thread: 126
  (TransferSender[414d51204946534d514431202020202054af77d920007628
  ])
  Class: com.ibm.wmqfte.io.bridge.BridgeFileFactoryHelperImpl
  Method: openTransfer
  Probe: FFDC_001
  Cause: java.lang.Exception: FTETransferReference:
  FTETransferReference [endPointType=SENDER,
  transferId=414d51204946534d514431202020202054af77d920007628,
  wmqConnection=null] is already open
  at
  com.ibm.wmqfte.io.bridge.BridgeFileFactoryHelperImpl.openTransfe
  r(BridgeFileFactoryHelperImpl.java:284)
  at
  com.ibm.wmqfte.io.FTEFileFactory.openTransfer(FTEFileFactory.jav
  a:901)
  at
  com.ibm.wmqfte.transfer.impl.TransferSenderRunnable.run(Transfer
  SenderRunnable.java:395)
  at java.lang.Thread.run(Thread.java:761)
  at com.ibm.wmqfte.thread.FTEThread.run(FTEThread.java:70)
  
  
  
  Filename:
  /var/mqm/mqft/logs/MFT/agents/AGENT/logs/ffdc/FFDC.FTE.201505131
  64353322.2900236004689889449.log
  Level: f750-FP-20130619-1001
  Time: 13/05/2015 16:43:53:322 GMT
  Thread: 126
  (TransferSender[414d51204946534d514431202020202054af77d920007628
  ])
  Class: com.ibm.wmqfte.io.bridge.BridgeFileFactoryHelperImpl
  Method: openTransfer
  Probe: FFDC_004
  Cause: com.ibm.wmqfte.bridge.session.BridgeContainerException:
  BFGBR0063E: An internal error has occurred. Request for a
  duplicate container for transfer Id
  414d51204946534d514431202020202054af77d920007628 occurred when
  already
  at
  com.ibm.wmqfte.bridge.session.BridgeSessionContainerManager.open
  Container(BridgeSessionContainerManager.java:91)
  at
  com.ibm.wmqfte.io.bridge.BridgeFileFactoryHelperImpl.openTransfe
  r(BridgeFileFactoryHelperImpl.java:296)
  at
  com.ibm.wmqfte.io.FTEFileFactory.openTransfer(FTEFileFactory.jav
  a:901)
  at
  com.ibm.wmqfte.transfer.impl.TransferSenderRunnable.run(Transfer
  SenderRunnable.java:395)
  at java.lang.Thread.run(Thread.java:761)
  at com.ibm.wmqfte.thread.FTEThread.run(FTEThread.java:70)
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects all users of WebSphere MQ Managed File
  Transfer 7.5 and 8.0 and MQ File Transfer Edition 7.0.4.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When a WebSphere MQ Managed File Transfer (MFT) agent detects a
  recoverable I/O exception for a managed transfer, that
  particular managed transfer is put into recovery. This involves
  requesting that the thread processing that managed transfers
  cleans up and stops. As part of the transfer recovery
  processing, a common restart point is negotiated between the
  source and destination agents for the transfer by exchanging
  recovery request/response messages. Once the negotiation is
  complete, a new thread responsible for processing that transfer
  is started.
  
  A TransferSender thread is associated with a single managed
  transfer in the source agent, and is used to control the overall
  source side processing for that transfer. There should only be
  one actively running TransferSender thread at any one time.
  
  If both the source and destination agents detected that a
  managed transfer required recovery at roughly the same period of
  time, then depending on the order of processing of the recovery
  request/response messages, the source agent could start two
  internal TransferSender threads for the same transfer.
  
  This situation could have occurred in the following scenario:
  
    1) A destination agent detected a recoverable I/O exception
  for a managed transfer and sent a recovery request message to
  the partner source agent for the transfer.
  
    2) The source agent began processing the recovery request
  message and requested the currently running TransferSender
  thread to stop. It then sent a recovery acceptance response
  message to the destination agent and prepared a new
  TransferSender thread to start.
  
    4) Before the TransferSender processed the internal stop
  request, it too detected the managed transfer required recovery
  and so sent a recovery request message to the destination agent.
  
    5) The source agent then received a recovery acceptance
  response message from the destination agent. It re-read the
  state message for the transfer from the SYSTEM.FTE.STATE queue
  and did not detect another, new TransferSender thread was
  waiting to run. As such, it created another new TransferSender
  thread for the same managed transfer and started it.
  
    6) The original TransferSender thread then finished processing
  the stop request and cleanup operations, which caused the first
  new TransferSender thread that was waiting to run to be started.
  
  At this point, there were now two new TransferSender threads
  running on the source agent for the same managed transfer, which
  is invalid and resulted in the FFDC files noted in the "Problem
  Description" section to be generated.
  

Problem conclusion

• The WebSphere MQ Managed File Transfer (MFT) code has been
  updated such that, if the source agent is already processing a
  recovery request from the partner destination agent then the
  currently running TransferSender thread for that particular
  managed transfer will not request recovery if it detects a
  problem. As such, the only new TransferSender thread that is
  created and started results from the recovery request message
  from the destination agent.
  
  ---------------------------------------------------------------
  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 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