Fixes are available
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
In WebSphere Application Server V7.0 and above, the following exception might be thrown if an EJB method is called within a global transaction that has been started by an application using the javax.transaction.TransactionManager interface. The problem will not occur if the EJB call is done within a container-managed global transaction or a global transaction that is started using the UserTransaction interface. The problem will also not occur in WebSphere Application Server V6.1 and below. . com.ibm.websphere.asynchbeans.WorkCompletedException: com.ibm.ws.asynchbeans.WorkRolledBackException: com.ibm.ws.LocalTransaction.RolledbackException: Resources rolled back due to unresolved action of rollback. at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:896) at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithE xecutionContextImpl.java:222) at com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:15 9) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1613) Caused by: com.ibm.ws.asynchbeans.WorkRolledBackException: com.ibm.ws.LocalTransaction.RolledbackException: Resources rolled back due to unresolved action of rollback. at com.ibm.ws.asynchbeans.services.tx.JTAServiceWithContext.pop(JTA ServiceWithContext.java:241) at com.ibm.ws.asynchbeans.J2EEServiceManager.popContext(J2EEService Manager.java:577) at com.ibm.ws.asynchbeans.J2EEContext.pop(J2EEContext.java:450) at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:880) ... 3 more Caused by: com.ibm.ws.LocalTransaction.RolledbackException: Resources rolled back due to unresolved action of rollback. at com.ibm.ws.LocalTransaction.LocalTranCoordImpl.cleanup(LocalTran CoordImpl.java:1380) at com.ibm.ws.LocalTransaction.LocalTranCoordImpl.end(LocalTranCoor dImpl.java:1428) at com.ibm.ws.LocalTransaction.LocalTranCurrentImpl.end(LocalTranCu rrentImpl.java:506) at com.ibm.ws.LocalTransaction.LocalTranCurrentSet.end(LocalTranCur rentSet.java:267) at com.ibm.ws.asynchbeans.services.tx.JTAServiceWithContext.pop(JTA ServiceWithContext.java:237) ... 6 more
Local fix
The application can be changed to start a transaction using another method (e.g. UserTransaction) rather than using the javax.transaction.TransactionManager interface in order to avoid the problem.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server with EJB applications using the * * javax.transaction.TransactionManager * * interface. * **************************************************************** * PROBLEM DESCRIPTION: EJB applications using the * * javax.transaction.TransactionManager * * interface may experience rollbacks or * * IllegalStateExceptions. * **************************************************************** * RECOMMENDATION: * **************************************************************** EJB applications using the javax.transaction.TransactionManager interface to begin, suspend, and resume transactions may experience unexpected transaction rollbacks or the following exception when calling an EJB method: java.lang.IllegalStateException: Cannot begin a LocalTransactionContainment. A LocalTransactionContainment is already active.
Problem conclusion
Use of the javax.transaction.TransactionManager API by an application may interfere with transaction management performed by the application server containers (EJB and/or Web), resulting in various failures, such as transactions being rolled back or an IllegalStateException when calling an EJB method. A change will be provided with this APAR, which may be enabled with the JVM custom property setting: com.ibm.websphere.ejbcontainer.PI10351=true. When enabled, the transaction management behavior of the EJB container will be restored to v6.1 behavior, which provides better toleration of an application using the javax.transaction.TransactionManager API. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.33, 8.0.0.9, and 8.5.5.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
PI10351
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-01-25
Closed date
2014-02-12
Last modified date
2014-02-12
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
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R700 PSY
UP
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022