Fixes are available
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
9.0.0.1: WebSphere Application Server traditional V9.0 Fix Pack 1
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
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
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
When the recovery log checks that the datasource is a non-transactional datasource it will return true if it finds that the datasource configured at any matching scope (matched by the JNDI lookup value) is non-transactional. ie if the datasource is non-transactional at the cell but has been redefined at the server as transactional the verification process will succeed when it should fail. Later, when the transaction service attempts to write data to its logs it will fail. The error message and call stack of the failure will be similar to the following output: [4/11/16 6:50:40:882 ICT] 00000001 XATransaction E J2CA0030E: Method enlist caught javax.transaction.SystemException: java.sql.SQLException: DSRA9350E: Operation Connection.commit is not allowed during a global transaction. at com.ibm.ws.tx.jta.RegisteredResources.enlistResource(RegisteredR esources .java:1149) ...
Local fix
Recovery log returns the true value of the datasource.
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere Application Server users that * * have configured the transaction service to * * store its logs in a database. * **************************************************************** * PROBLEM DESCRIPTION: J2CA0030E occurs due to DSRA9350E: * * Operation Connection.commit is not * * allowed during a global transaction. * **************************************************************** * RECOMMENDATION: * **************************************************************** The datasource specified via its jndi name in the custom string for the transaction log directory must be configured to be non-transactional. The transaction service verifies that the the datasource is configured correctly on initialization and should generate CWRLS0008 and CWRLS0009 messages indicating that accessing the recovery logs has failed if the datasource is transactional. If the jndi name of the datasource is specified at multiple scopes then the effective datasource configuration in use is that for the narrowest scope. The algorithm that verifies that the datasource is non-transactional should perform verification only against the datasource defined at the narrowest scope, however if this datasource is transactional but a non-transactional datasource with the same jndi name is defined at a wider scope then the verification erroneously succeeds.
Problem conclusion
The algorithm that verifies that the datasource is configured as non-transactional was corrected to correctly process the datsource defined at the narrowest scope. The fix for this APAR is currently targeted for inclusion in fix packs 8.5.5.10 and 9.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
PI61081
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-04-19
Closed date
2016-07-12
Last modified date
2016-07-13
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
R850 PSY
UP
Document Information
Modified date:
03 May 2022