PM50996: MQ MESSAGE IS ROLLED BACK TO THE INPUT QUEUE EVEN THOUGH MAP COMPLETES SUCCESSFULLY

APAR status

• Closed as program error.

Error description

• MQ message is rolled back to the input queue even though map
  completes successfully.
  
  The map runs without any error or warning but the MQ message is
  rolled back to the input queue.  The backout count is "1".
  After a restart of the launcher, the message is read again.
  The message is still found on the input queue even though an
  error queue has been defined.
  

Local fix

• WTXCQ - WTX00039209
  GK / PB
  Circumvention: None
  

Problem summary

• Users Affected:
  WebSphere Transformation Extender that encounter MQ Commit
  failures in their maps.
  
  Problem Description:
  The WTX MQ Adapter does not move messages to an error queue when
  an MQ Commit operation fails.
  
  Platforms Affected:
  ALL
  

Problem conclusion

• WTX MQ Adapter now rolls back transactions to an error queue (if
  provided) in the event that a commit operation fails.  Before
  this fix, the MQ Commit failure would cause the message to
  remain on the queue and could get unexpectedly re-processed on
  Launcher restart.
  
  Delivered in:
  8.1.0.6, 8.2.0.6, 8.3.0.5, 8.4.0.0
  

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

  WEBSPHERE LAUNC

• Fixed component ID

  5724M4011

Applicable component levels

• R810 PSY

     UP

• R820 PSY

     UP

• R830 PSY

     UP

• R840 PSY

     UP