Fixes are available
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
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.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
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.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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
The failing scenario involves the following: - An application which contains EJB 2.x CMP beans is deployed on WebSphere Application Server v6.1.0.35 - CMP Connection Factories are created during application deployment - Post install modifications are performed, such as mapping web servers to web modules or changing the classloader policy (this is the important step which causes the problem) - New, unexpected cmpConnectionFactory elements appear in the ibm-ejb-jar-bnd.xmi file - The new CMP Connection Factories can result in the following IllegalResourceIn2PCTransactionException [3/29/11 10:58:19:351 EDT] 0000004f RegisteredRes E WTRN0062E: An illegal attempt to use multiple resources that have only one-phase capability has occurred within a global transaction. [3/29/11 10:58:19:353 EDT] 0000004f RegisteredRes < enlistResource (SPI) Exit com.ibm.ws.Transaction.IllegalResourceIn2PCTransactionException: Illegal attempt to enlist multiple 1PC XAResources at com.ibm.ws.Transaction.JTA.RegisteredResources.enlistResource(Re gisteredResources.java:417) at com.ibm.ws.Transaction.JTA.TransactionImpl.enlistResource(Transa ctionImpl.java:3208) at com.ibm.ws.Transaction.JTA.TranManagerSet.enlistOnePhase(TranMan agerSet.java:449) at com.ibm.ejs.j2c.LocalTransactionWrapper.enlist(LocalTransactionW rapper.java:591) at com.ibm.ejs.j2c.ConnectionManager.lazyEnlist(ConnectionManager.j ava:1933) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.lazyEnlist(W SRdbManagedConnectionImpl.java:2248) at com.ibm.ws.rsadapter.cci.WSRdbConnectionImpl.enlistIfNecessary(W SRdbConnectionImpl.java:720) at com.ibm.ws.rsadapter.cci.WSInteractionImpl.execute(WSInteraction Impl.java:490) at com.ibm.ws.rsadapter.cci.WSRelationalRAAdapter.executeCreate(WSR elationalRAAdapter.java:356) at com.ibm.ws.ejbpersistence.dataaccess.DataAccessRequestImpl.execu te(DataAccessRequestImpl.java:193)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V6.1, V7.0 and V8.0 * **************************************************************** * PROBLEM DESCRIPTION: Empty container-managed persistence * * (CMP) connection factory bindings are * * created after an application * * containing CMP 2.x beans is edited. * **************************************************************** * RECOMMENDATION: * **************************************************************** When an edit operation such as changing the classloader policy or changing the server of a module is performed on an application containing container-managed persistence (CMP) 2.x beans with a data source configured at the Enterprise JavaBeans (EJB) 2.x module level, an empty CMP connection factory binding is created for each CMP 2.x bean after an edit. The empty binding results in the following exception: com.ibm.ws.Transaction.IllegalResourceIn2PCTransactionException: Illegal attempt to enlist multiple 1PC XAResources
Problem conclusion
The edit logic has been corrected to not create an empty CMP connection factory binding at the bean level if a binding is provided at the module level. The fix for this APAR is currently targeted for inclusion in fix packs 6.1.0.41, 7.0.0.19 and 8.0.0.1. 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
PM38547
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-05-06
Closed date
2011-05-20
Last modified date
2014-05-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
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