Fixes are available
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 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
APAR status
Closed as program error.
Error description
When a new transaction is started one that is running will be suspended and resumed once control has been returned. Information on whether a new Local transaction should be started is stored in the transaction manager. At this point the new transaction is being started (in between the preEnd and postEnd methods) the local transaction information has been placed on the thread local context as it has completed but not yet cleaned up. This context is being overwritten by the new transaction that is started.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V6.1 and V7.0 * **************************************************************** * PROBLEM DESCRIPTION: Global tx commit failed: * * java.lang.IllegalStateException: * * No transaction associated with this * * thread. When a second transaction is * * started inside the afterCompletion * * method of the first. The * * ServiceRegistryActivityLoggerBean has * * a synchronizationCallback that * * initiates transactional work during * * the after completion of an existing * * transaction. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a new transaction is started one that is running will be suspended and resumed once control has been returned. Information on whether a new Local transaction should be started is stored in the transaction manager. At the point this new transaction is being started (inbetween the preEnd and postEnd methods) the Local transaction information has been placed on the thread local context as it has completed but not yet been cleaned up. This context is being overwritten by the new transaction that is started.
Problem conclusion
The LTCUOWCallback has four main methods, preBegin, postBegin, preEnd and postEnd, there was originally one WSThreadLocal context for the whole class which is reset in each of the pre... methods. The WSThreadLocal context in the LTCUOWCallback has now been split into two halves. One for the begin methods and one for the end methods, thus preventing any later preBegin calls from nullifying the context which is still to be used in a postEnd call. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.17. 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
PM25461
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
2010-10-28
Closed date
2010-12-08
Last modified date
2010-12-08
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
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
Document Information
Modified date:
27 October 2021