Fixes are available
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
The following error may occur during transaction association... java.lang.RuntimeException: javax.resource.spi.work.WorkCompletedException: Already have an association or already prepared, error code: 2 at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:381) at com.ibm.ejs.j2c.work.WorkManagerImpl.doWork(WorkManagerImpl.java :176) at com.ibm.test.adapter.execute(Test.java:34) at com.ibm.test.adapter.run(Test.java:21) at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:399) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1646) Caused by: javax.resource.spi.work.WorkCompletedException: Already have an association or already prepared, error code: 2 at com.ibm.tx.jta.TxExecutionContextHandler.associate(TxExecutionCo ntextHandler.java:180) at com.ibm.ws.tx.jta.TxExecutionContextHandler.associate(TxExecutio nContextHandler.java:66) at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:322)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere Application Server users of JCA * * Transaction inflow management * **************************************************************** * PROBLEM DESCRIPTION: javax.resource.spi.work.WorkCompletedEx * * ception when importing a transaction * * from an external EIS via a JCA * * Resource Adapter * **************************************************************** * RECOMMENDATION: * **************************************************************** A thread importing an IIOP request containing a JTS transaction context attempts to match the XID of the incoming transaction to that of existing transactions. The method that obtains the XID from the transaction allocated the XID if not already set. However a transaction imported from JCA Resource Adapter was already in the set of existing transactions but its XID was not yet set. Therefore a race condition occured whereby the thread importing the IIOP request could set the XID of the JCA imported transaction to an incorrect value. Later, when the thread running the JCA imported transaction returned, this incorrect XID set in the transaction was used to disassociate the imported JCA transaction from the thread. The association keyed off the incorrect XID was not found and therefore the dissocation did not occur. Further work imported from the EIS under the same transaction then failed since the transaction service state indicated that the transaction was already associated with another thread and the following exception occured: javax.resource.spi.work.WorkCompletedException: Already have an association or already prepared, error code: 2
Problem conclusion
The transaction service code was changed to eliminate the race condition. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.35, 8.0.0.10 and 8.5.5.4. Please refer to the Recommended Updatespage for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI12571
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-02-26
Closed date
2014-06-27
Last modified date
2014-06-27
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
R700 PSY
UP
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022