PM69206: MDB MESSAGE IS NOT BACKED OUT TO BACKOUT REQUEUE WHEN USING BEAN MANAGED TRANSACTION (BMT) DEMARCATION

8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
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

• Customer reported that during recovery processing of MQ JMS
  Provider
  an expected rollback to backup requeue did not take place on WAS
  on z/OS V8 as it had on V7.
  .   They had a listener port configured such that after
  three delivery attempts to an MDB the message should be rolled
  back, however, it was not.
  
  Level three assessment is that they are using a different
  transport.  On V7 the customer is using a BINDINGS mode
  connection to MQ and on V8 they are using a Bean Managed
  Transaction
  (BMT) demarcation.  APAR fixes the problem of failing to recover
  in
  Bean Managed mode with a non transacted session.
  

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.                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: JMS messages are not rolled back to     *
  *                      the input queue after an exception is   *
  *                      thrown from a bean-managed              *
  *                      transaction message-driven bean.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The message-driven bean listener ports do not call recover on
  the JMS session after a RuntimeException is thrown from a
  bean-managed transaction message-driven bean. This causes the
  message to not be redelivered to the message-driven bean.
  

Problem conclusion

• The listener port has been updated to call recover on the JMS
  session when the message-driven bean throws a RuntimeException.
  
  APAR PM69206 is currently targeted for inclusion in
  Service Level (Fix Pack)  of WebSphere
  Application Server
  
  APAR PM69206 is currently targeted for inclusion in
  Fix Packs 8.0.0.6 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