IT06110: WMQ MANAGED FILE TRANSFER 7.5 SOURCE AGENT PRODUCES FFDC WMQAPIFAILUREEXCEPTION: CC=2 RC=2033 OP=_GET.

Fix Pack 8.0.0.2 for WebSphere MQ V8.0

APAR status

• Closed as program error.

Error description

• A source agent generates an FFDC file and ends abnormally. The
  FFDC file generated contains the following information:
  
  Filename: FFDC.FTE.20141218113936383.2511669970418637745.log
  Level: f750-FP-20140428-1317
  Time: 18/12/2014 11:39:36:383 GMT
  Thread: 41
  (RestartSender414d51204d465437355f434d44202020844e915420002402)
  Class: com.ibm.wmqfte.statestore.impl.FTERestartAgentRunnable
  Instance: 67406740
  Method: run
  Probe: FFDC_001
  Cause: com.ibm.wmqfte.wmqiface.WMQApiFailureException: cc=2
  rc=2033 op=_get - MQGET
  
  com.ibm.wmqfte.wmqiface.WMQApiFailureException: cc=2 rc=2033
  op=_get - MQGET
  at
  com.ibm.wmqfte.wmqiface.WMQQueueImpl._get(WMQQueueImpl.java:304)
  at
  com.ibm.wmqfte.wmqiface.WMQQueueImpl.get(WMQQueueImpl.java:243)
  at
  com.ibm.wmqfte.statestore.impl.FTEStateStorePersistence$FTEMutab
  leSenderStateRef.getStateFromPersistentStore(FTEStateStorePersis
  tence.java:286)
  at
  com.ibm.wmqfte.statestore.impl.FTEStateStorePersistence$FTEMutab
  leSenderStateRef.getFTEMutableSenderState(FTEStateStorePersisten
  ce.java:255)
  at
  com.ibm.wmqfte.statestore.impl.FTEStateStorePersistence$Transfer
  RequestQueue.take(FTEStateStorePersistence.java:577)
  at
  com.ibm.wmqfte.statestore.impl.FTEStateStorePersistence$SenderTr
  ansferRequestMap.get(FTEStateStorePersistence.java:813)
  at
  com.ibm.wmqfte.statestore.impl.FTEStateStorePersistence.getSende
  rState(FTEStateStorePersistence.java:1895)
  at
  com.ibm.wmqfte.statestore.impl.FTEStateStorePersistence.getMutab
  leSenderState(FTEStateStorePersistence.java:1696)
  at
  com.ibm.wmqfte.statestore.impl.FTEStateStoreImpl.restartSender(F
  TEStateStoreImpl.java:2678)
  at
  com.ibm.wmqfte.statestore.impl.FTERestartAgentRunnable.run(FTERe
  startAgentRunnable.java:85)
  at java.lang.Thread.run(Thread.java:761)
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects all users of WebSphere MQ Managed File
  Transfer.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When a WebSphere MQ Managed File Transfer (MFT) destination
  agent has written all of the transfer data to the destination
  file(s), such that the transfer of data is complete, it sends a
  "Completed" acknowledgement message to the source agent. The
  source agent then processes this "Completed" message in order to
  finish the processing for the transfer. This includes deleting
  the source file for the transfer (if requested) and publishing
  the transfer complete log message to the SYSTEM.FTE topic, for
  example.
  
  If the "Completed" acknowledgement message was processed after
  the source agent had put the transfer in recovery (e.g., because
  a network connection between the agent and its agent queue
  manager had gone down), the source agent might need to read the
  state message for this transfer from its SYSTEM.FTE.STATE.
  queue.
  
  When this happened, the transfer state message was read under
  the same syncpoint under which the "Completed" acknowledgement
  message was being processed. After populating an internal state
  object, the transfer state message was put back onto the source
  agent's STATE queue (again
  under the same syncpoint). This syncpoint wasn't committed until
  all of the processing for this transfer (and the "Completed"
  message) was finished.
  
  Because the transfer was in a recovery state, a new thread was
  started to perform the final processing for this transfer. This
  thread created its own connection to the agent's WebSphere MQ
  queue manager and attempted to read the state message for the
  transfer from the agent's STATE queue. However, because the
  transfer state message was already locked under the same
  syncpoint used for processing the "Completed" acknowledgement
  message, the agent's WebSphere MQ queue manager returned a 2033
  (MQRC_NO_MESSAGE_AVAILABLE) reason code.
  
  This caused the agent to generated an FFDC file and end
  abnormally with entries such as the following written to the
  agent's output0.log file:
  
  FFDCImpl E BFGUT0002E: An internal error has occurred. Product
  failure data was captured in file
  "FFDC.FTE.20141218113936383.2511669970418637745.log".
  FTERestartAge E BFGSS0037E: An internal error occurred. The
  exception is: 'cc=2 rc=2033 op=_get - MQGET'
  AgentRuntime E BFGAG0171E: The agent has ended abnormally with
  return code 70.
  

Problem conclusion

• The WebSphere MQ Managed File Transfer agent code has been
  updated such that when a source agent is processing a
  "Completed" acknowledgement message and needs to read the state
  message for the completed transfer from the agent's STATE queue,
  it does so using a new connection and syncpoint that is separate
  to that used to process said "Completed" acknowledgement
  message.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.5       7.5.0.6
  v8.0       8.0.0.2
  
  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