IT05585: WEBSPHERE MQ FILE TRANSFER PROTOCOL BRIDGE AGENTS IN RECOVERY PROCESSING FAIL TO SEND THE PROPER "PROGRESS" ACKNOWLEDGMENT

APAR status

• Closed as program error.

Error description

• Problem: Some WMQ MFT transfers complete but javacores
  show the SenderEnd thread does not end, but remains in a loop.
  The transfer log from MQ Explorer indicates a "Success" status
  but the transfer log does not contain the expected "Progress"
  and"Completed" messages.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of the WebSphere MQ V7.5 Managed File
  Transfer component.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The following sequence of events led up to the issue reported in
  this APAR:
  
  - A Destination Agent received a managed transfer request, and
  started an internal TransferReceiver thread to process it.
  - Before the Destination Agent had sent a "Progress" message
  containing audit information to the Source Agent, the
  Destination Agent received a "Resynchronising" message from the
  Source Agent. This message indicated that the Source Agent had
  decided to put the managed transfer into recovery.
  
  - The Destination Agent created a new internal TransferReceiver
  thread to handle the recovery situation.
  - The new TransferReceiver thread started, and then waited for
  the first TransferReceiver thread to complete.
  - The first TransferReceiver stopped before it had sent a
  "Progress" message to the Source Agent.
  - The new TransferReceiver resumed the managed transfer. It
  checked the state of the managed transfer, and determined that
  it had completed. This caused the new TransferReceiverf to send
  a "Completed" message for the transfer to the Source Agent.
  
  - The Source Agent received the "Completed" message, and starts
  a SenderEnd thread for the managed transfer.
  - The SenderEnd thread checked if the Source Agent had received
  a "Progress" message containing remote audit information about
  the managed transfer from the Destination Agent. It hadn't, so
  the SenderEnd thread waited for the "Progress" message to
  arrive.
  
  Because the "Progress" message was never sent by the Destination
  Agent, the SenderEnd thread for the managed transfer within the
  Source Agent never completed. As a result of this, any programs
  specified in the postSourceCall for the managed transfer were
  not executed.
  

Problem conclusion

• The WebSphere MQ V7.5 Managed File Transfer component has been
  updated so that, if a managed transfer is put into recovery by a
  Source Agent, the Destination Agent will send a "Progress"
  message containing remote audit information for the managed
  transfer if necessary before resuming the transfer.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.5       7.5.0.6
  v8.0       8.0.0.3
  
  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