PK84748: WMSG0031E EXCEPTION PROCESSING JMS MESSAGE FOR MDB; A ROLLBACK (WLTC0032W) MAY BE SEEN DURING CLEANUP OF THE LOCAL TRANSACTION

Fixes are available

APAR status

Closed as program error.

Error description

The problem occurs for bean-managed transactions, with
message-driven beans listening against a queue on a WebSphere MQ
queue manager via a listener port, with an RRS enabled
connection factory on z/OS.  The WebSphere Application Server
messaging code is failing to inform the transaction manager that
the consumption of the message by the listener port should occur
under RRS transaction coordination.

Following warning/exception messages may be seen:

BBOO0221W: WLTC0032W: One or more local transaction resources
were rolled back during the cleanup of a
LocalTransactionContainment.

BBOO0221W: WMSG0031E: Exception processing JMS Message for MDB
MDBTestBean, JMSDestination jms/JMSTestDestination
 2_QueueDest : javax.ejb.TransactionRolledbackLocalException:  ;
nested exception is:
com.ibm.websphere.csi.CSITransactionRolledbackException

Local fix

```
N/A.
```

Problem summary

****************************************************************
* USERS AFFECTED:  Users of IBM WebSphere Application Server   *
*                  V7.0 using WebSphere MQ as a messaging      *
*                  provider                                    *
****************************************************************
* PROBLEM DESCRIPTION: Message-driven bean (MDB) applications  *
*                      using bean managed transactions fail    *
*                      to consume messages, when listening to  *
*                      a WebSphere MQ queue via a listener     *
*                      port.                                   *
*                      A TransactionRolledbackLocalException   *
*                      might be thrown committing the          *
*                      transaction, and the messages return    *
*                      to the queue when the application       *
*                      server is shut down.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The listener port code does not inform the transaction manager
that RRS coordinated work is performed within WebSphere MQ by
the listener port. This is required due to an optimization in
WebSphere Application Server Version 7.0 that defers some
native processing until an RRS enabled resource is enlisted in
the local transaction context.
The failure to inform the transaction manager of the RRS
involvement results in a TransactionRolledbackLocalException
exception being thrown while committing the application's
bean-managed transaction. The transaction is rolled back.
The TransactionRolledbackLocalException exception is only
observed for a BINDINGS transport WebSphere MQ connection.

In addition, the transasction that consumed the message within
WebSphere MQ is left uncommitted by the listener port.
This causes all messages consumed from the WebSphere MQ
destination to be rolled back when the application server is
terminated. This is caused by the WebSphere MQ Version 7.0
resource adapter silently ignoring a call to acknowledge a
message when the JMS ServerSession is incorrectly configured
in AUTO_ACKNOWLEDGE mode.
Previous versions of WebSphere MQ translated the
acknowledgement into an MQCMIT action, even though the
acknowledge mode was set incorrectly.
The manual acknowledgement of a message by the listener port
is only performed on z/OS.
The rollback of messages on application server shut down can
be observed for a CLIENT or BINDINGS transport WebSphere MQ
Connection.

Problem conclusion

The fix for this APAR allows a message listener to correctly
invoke an MDB from a WebSphere MQ queue with a bean-managed
transaction context on z/OS.

The fix causes the listener port to inform the transaction
manager that the consume of the message will be performed
using an RRS coordinated local transaction, when the connection
uses a BINDINGS transport on z/OS.

The fix also causes the listener port to establish the
ServerSession in CLIENT_ACKNOWLEDGE mode on z/OS, so that the
MQCMIT is performed as part of message acknowledgement in the
WebSphere MQ Version 7.0 resource adapter.

APAR PK84748 is currently targeted for inclusion in Service
Level (Fix Pack) 7.0.0.5 of IBM WebSphere Application Server.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PK84748
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-04-15
Closed date
2009-06-01
Last modified date
2009-08-03

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

R700 PSY UK48200
UP09/07/27 P F907

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK84748: WMSG0031E EXCEPTION PROCESSING JMS MESSAGE FOR MDB; A ROLLBACK (WLTC0032W) MAY BE SEEN DURING CLEANUP OF THE LOCAL TRANSACTION

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY UK48200

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

Document Information

Share your feedback

Need support?