PM43639: EJB 3.0 MDB FAILS TO ROLLBACK A MESSAGE WHEN A RUNTIMEEXCEPTION OCCURS

Fixes are available

APAR status

Closed as program error.

Error description

Using an EJB 3.0 Message Driven Bean (MDB) with no
transaction-type set in the deployment descriptor, if a
RuntimeException occurs the message driving the bean is not
rolled back onto the queue.  Instead it is consumed.  Any
other resources enlisted with the transaction during the MDB's
onMessage method are rolled back as expected.

Local fix

workaround for this would be to specify the transaction-type
explictly for the 3.0 application.  This can be done by
editing the DD using whatever tool was used to create it.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: Using EJB 3.0 Message Driven Beans, a   *
*                      RuntimeException does not cause the     *
*                      message to rollback.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
During the setup of the Message Driven Bean, a programming
error meant that the context was incorrectly believed to be
EJB 2.1.  The transaction-type attribute in the deployment
descriptor of 2.1 EJBs was a mandatory field, but not in EJB
3.0.  As a result, a default of 'bean managed' was used
instead of the correct EJB 3.0 default of 'container managed'.
Consequently, 'bean managed' transactional behaviour is
observed and the message is not rolled back when a
RuntimeException occurs and there is no explcit rollback
instruction from the application bean.

Problem conclusion

This APAR resolves the problem by ensuring that the EJB version
if correctly detected.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.41, 7.0.0.21 and 8.0.0.3.  Please refer to the
Recommended Updates page for delivery information:

http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM43639
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-07-13
Closed date
2011-07-30
Last modified date
2011-07-30

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

PM47547

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
R800 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021

Tips

PM43639: EJB 3.0 MDB FAILS TO ROLLBACK A MESSAGE WHEN A RUNTIMEEXCEPTION OCCURS

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

R800 PSY

Document Information

Share your feedback

Need support?