PQ69904: Provide correct Transaction Status if BMT
calls CMT Bean
Downloadable files
Abstract
BMT session Bean have incorrect Transaction status after
method call on CMT session Bean that changed the Transaction status.
Download Description
A BMT Session Bean starting a UserTransaction then makes some direct
JDBC calls then calls a method on a CMT Session Bean (which has REQUIRED
transaction setting) which updates an EntityBean and then marks the
trasanction for rollback. Now at this point when the
control returns back to the BMT Session Bean the transaction status is
still ACTIVE. Infact it should have been as MARKED_ROLLBACK (because it
was marked for rollback by the CMT Session Bean).
A BMT Bean starts a transaction and calls a CMT Bean that calls
setRollbackOnly() and returns to the BMT Bean. If the BMT Bean now calls
UserTransaction.getStatus() it will receive an Active status rather than
MarkedForRollback. This fix corrects this situation.
A companion EJB Container fix
(WAS_EJBContainer_04-21-2003_5.0.0_cumulative.jar or later) is also
required for the EJB Container to enable the JTS fix.
This fix also re-delivers the fix for PQ68703 - Null Pointer Exception due
to superior and subordinate timeout's.
Prerequisites
Please download the UpdateInstaller below to install this fix.