PQ61013: GETTING TRANSACTION STATUS IN AN EJB ALWAYS RETURNS ACTIVE EVEN WHEN THE TRANSACTION ATTRIBUTE IS NOT_SUPPORTED.

APAR status
Closed as user error.

Error description
When the transaction attribute of an EJB is NOT_SUPPORTED, then
In the JSP, the getStatus() returns a 6 (no transaction)
In the EJBs, the getStatus() returns a 0 (transaction started)
The EJB status should be the same as the JSP status.
Local fix Problem summary Problem conclusion Temporary fix Comments
Upon investigating the root cause of this problem it became
clear that the error reported is because the code in
question was accessing the UserTransaction interface from a
container-managed transaction demarcated bean. The use of the
UserTransaction interface in such a case is forbidden by the
Enterprise Java beans V1.1 specification as documented in
section 11.3.4 'Enterprise beans using container-managed
transactions'.
The bean should be deployed using bean-managed transaction
demarcation.
APAR information
APAR number PQ61013
Reported component name WEBSPHERE AE AI
Reported component ID 5630A2200
Reported release 400
Status CLOSED USE
PE NoPE
HIPER NoHIPER
Submitted date 2002-05-10
Closed date 2002-05-22
Last modified date 2002-05-22

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information

Applicable component levels


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ61013
IBM Group: Software Group
Modified date: May 22, 2002