Explanation of active transaction status codes and defect PQ76402
 Technote (troubleshooting)
 
Problem(Abstract)
An information center for z/OS® article called "Managing active transactions" explains the status codes for an active transaction; however, this information is not included in the information centers for the other WebSphere® editions. Furthermore, the Manage Transactions console shows transaction status 10, 11,12 and 13, which are not explained anywhere and cannot be finished.
 
Cause
This is a problem in WebSphere version 5.0.2 because the console incorrectly passes internal transaction status codes that are not intended for external viewing. The article in the information center details the status codes as defined by the specification in the javax.transaction.Status file. The internal status codes 10, 11, 12, and 13 specify a finer level of granularity, but are not intended to be seen outside of the transaction. The list of internal transaction status codes shows little correlation to the external status codes, which you can see.
For reference:

Internal codes
External codes
0
None
0
Active
1
Present
1
Marked for rollback
2
Active
2
Prepared
3
Inactive
3
Committed
4
Preparing
4
Rolled back
5
Prepared
5
Unknown
6
Committing
6
None
7
Committed
7
Preparing
8
Commit complete
8
Committing
9
Before abort
9
Rolling back
10
Aborting
11
Aborted
12
Abort complete
13
Finished
 
Resolving the problem
This is corrected in PQ76402, which is shipped in Cumulative Fix 1 and higher for 5.0.2. The internal codes are no longer viewable by the user.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Java Transaction Service (JTS)
Operating system(s): Windows
Software version: 5.0.2
Software edition:
Reference #: 1148435
IBM Group: Software Group
Modified date: Jan 30, 2007