PM67444: MDB MESSAGE IS NOT BACKED OUT TO BACKOUT REQUEUE (WHEN USING CLIENT CONNECTION).

8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• When an MDB throws a RuntimeException during processing, the
  MQ message did not roll back to the queue when using a
  non transacted MDB and a CLIENT mode connection to MQ.
  

Local fix

• Use BINDINGS mode connection on z/WAS V8.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.0 and V8.5 for z/OS using a non   *
  *                  transacted MDB consuming from a WebSphere   *
  *                  MQ queue with a CLIENT transport.           *
  ****************************************************************
  * PROBLEM DESCRIPTION: Message consumed by MDB did not         *
  *                      rollback to the queue when the MDB      *
  *                      threw a RuntimeException.               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When an MDB on WebSphere Application Server for z/OS consumes
  a message from WebSphere MQ using the CLIENT transport, the
  message will be consumed under a CLIENT_ACKNOWLEDGE JMS
  session if the transaction type of the MDB is NON_TRANSACTED.
  Under normal operation every message is acknowledged after the
  MDB completes normally.
  If a RuntimeException is thrown during MDB processing, the
  message will not be acknowledged. However, because the JMS
  session is not asked to recover, the MQ message consumed but
  not acknowledged will remain locked on the MQ queue until the
  MQ connection which consumed it disconnects. This will only
  happen when the MDB stops.
  

Problem conclusion

• The code has been altered to ensure that if a RuntimeException
  occurs during the processing of a NON_TRANSACTED MDB
  consuming messages from MQ on z/OS, the underlying JMS session
  is asked to recover. This ensures the message rolls back onto
  the MQ queue and is available for reprocessing.
  
  APAR PM67444 is currently targeted for inclusion in
  Fix Packs 8.0.0.5 and 8.5.0.1 of WebSphere Application
  Server.
  
  Please refer to the Recommended Updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  
  In addition, please refer to URL:
  http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
  for Fix Pack PTF information.
  

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 FOR Z

• Fixed component ID

  5655I3500

Applicable component levels

• R800 PSY

     UP