IT05587: WMQFTE AGENT HANGS REPORTING MQRC 2080 (MQRC_TRUNCATED_MSG_FAILED) UNDER HEAVY LOAD

WebSphere MQ File Transfer Edition V7.0 Fix Pack 7.0.4.5

APAR status

• Closed as program error.

Error description

• When using WebSphere MQ FTE v7.0.4.2 under heavier loads the FTE
  agent appears to hang. MQ error 2080 (MQRC_TRUNCATED_MSG_FAILED)
  is reported along with errors in the output0.log:
  
  FFDCImpl E BFGUT0002E: An internal error has occurred. Product
  failure data was capture in the file "FFDC.FTE.2014...."
   MonitorImpl E BFGDM0083E: An internal error has occurred. The
  exception is: cc=1 rc=2080 op=_get - MQGET
   AgentRuntime E BFGAG0061E: The agent ended abnormally
  
  An FFST is also written containing:
  
  Class: com.ibm.wmqfte.management.MonitorImpl
  Method: run
  Probe: FFDC_001
  Cause: com.ibm.wmqfte.wmqiface.WMQApiWarningException: cc=1
  rc=2080op=_get - MQGET
  com.ibm.wmqfte.wmqiface.WMQApiWarningException: cc=1 rc=2080
  op=_get -
  MQGET
      at com.ibm.wmqfte.wmqiface.WMQQueueImpl._get
  (WMQQueueImpl.java:542)
      at com.ibm.wmqfte.wmqiface.WMQQueueImpl.get
  (WMQQueueImpl.java:478)
      at com.ibm.wmqfte.wmqiface.WMQQueueImpl.get
  (WMQQueueImpl.java:337)
  

Local fix

• na
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of WebSphere MQ File Transfer Edition
  (FTE) 7.0.4 and WebSphere MQ Managed File Transfer (MFT) 7.5 and
  8.0.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  This problem occurs when two MQGETS on the same thread both fail
  with MQ error 2080 (MQRC_TRUNCATED_MSG_FAILED).
  
  The first MQGET specifies a buffer size that is smaller than the
  size of the available message. The second MQGET specifies a
  buffer large enough for the original message and expects to be
  able to get it, but again the message size is too large. This
  was caused by a timing window where another thread destructively
  got the original message that the first thread was attempting to
  get.
  
  The second get on the first thread is therefore presented with
  the next message for processing, which in the reported case was
  too large to fit into the supplied buffer, and so the 2080
  MQRC_TRUNCATED_MSG_FAILED error was returned.
  

Problem conclusion

• The WebSphere MQ File Transfer Edition and WebSphere MQ Managed
  File Transfer code has been updated to accept truncated
  messages, as it is only interested in reading the message header
  data. If due to truncation of the message the full message
  header is not received, the MQGET call is issued again with a
  larger buffer so that the entire message header data can be
  read.
  
  If the message is no longer available during this MQGET, the
  message is ignored and FTE moves on to process the next message.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.0       7.0.4.5
  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 FILE TRANSF

• Fixed component ID

  5724R1000

Applicable component levels

• R704 PSY

     UP