Fixes are available
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
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: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
When using unshared connections J2C handle list code attempts to reassociate to all handles on handle list even if handles belong to another transaction that is suspended. This problem only occurs when using the Transaction Control Inerface to start a LTC or a User Transaction from with in a LTC. THe problem happens after the LTC is suspened and the new transaction context begins. Following J2C error message are continuously logged in SystemOut.log; --- J2CA0058E: The ConnectionManager was unable to associate Connection com.ibm.ws.rsadapter.jdbc.WSJdbcConnection@13f013f0 resource.ResourceException: Current UOW does not match the UOW with whi ch the ManagedConnection is already enlisted. at com.ibm.ejs.j2c.ConnectionManager.reAssociate(ConnectionManager. jav a:1588) ---
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V6.1 who use unshared connections * * with nested transaction * **************************************************************** * PROBLEM DESCRIPTION: J2CA0058E: The ConnectionManager was * * unable to associate Connection * * Current UOW does not match the UOW * **************************************************************** * RECOMMENDATION: * **************************************************************** When using unshared connections Java 2 Connector (J2C) handle list code attempts to reassociate to all handles on handle list even if handles belong to another transaction that is suspended. This problem only occurs when using the Transaction Control Inerface to start a LTC or a User Transaction from with in a LTC. The problem happens after the LTC is suspended and the new transaction context begins. The following J2C error message are continuously logged in SystemOut.log; --- J2CA0058E: The ConnectionManager was unable to associate Connection com.ibm.ws.rsadapter.jdbc.WSJdbcConnection@13f013f0 resource.ResourceException: Current UOW does not match the UOW with which the ManagedConnection is already enlisted
Problem conclusion
This problem was fixed to correctly handle this situation. The fix for this APAR is currently targeted for inclusion in fix pack 6.1.0.21 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
PK69099
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-07-16
Closed date
2008-09-10
Last modified date
2008-09-10
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
Document Information
Modified date:
29 December 2021