PQ69904: BMT SESSION BEAN HAVE INCORRECT TRANSACTION STATUS AFTER METHOD CALL ON CMT SESSION BEAN THAT CHANGED THE TRANSACTION STATUS.

 Fixes are available

PQ69904: Provide correct Transaction Status if BMT calls CMT Bean
5.0.2: WebSphere Application Server Version 5.0 Fix Pack 2 (Version 5.0.2)



APAR status
Closed as program error.

Error 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).
Local fix
The defect is discoveried in the proof of concept process.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server BMT Beans       *
*                 calling CMT Beans                            *
****************************************************************
* PROBLEM DESCRIPTION: Provide correct Transaction Status if   *
*                      BMT calls CMT Bean.                     *
*                                                              *
*                                                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Provide correct Transaction Status if BMT calls CMT 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.
Problem conclusion
Provide interface for EJB container to notify JTS of
CMT rollback.
Temporary fix
PQ69904 supplied requires also
WAS_EJBContainer_04-21-2003_5.0.0_cumulative.jar
Comments
APAR information
APAR number PQ69904
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-01-15
Closed date 2003-05-07
Last modified date 2003-05-07

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
CORDIMPL UOWCOORD UTXIMPL      

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ69904
IBM Group: Software Group
Modified date: May 7, 2003