Fixes are available
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
17.0.0.1: WebSphere Application Server Liberty 17.0.0.1
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
17.0.0.2: WebSphere Application Server Liberty 17.0.0.2
17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12
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
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
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
CWRLS0009E occurs due to failure Exception calling setTransactionIsolation on a JDBC connection. A typical callstack is shown below: CWRLS0009E: Details of recovery log failure: java.sql.SQLException: READ_COMMITTED and SERIALIZABLE are the only valid transaction levels at oracle.jdbc.driver.PhysicalConnection.setTransactionIsolation(Ph ysicalConnection.java:5376) at oracle.jdbc.OracleConnectionWrapper.setTransactionIsolation(Orac leConnectionWrapper.java:185) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.setTransacti onIsolation(WSRdbManagedConnectionImpl.java:5650) at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.setTransactionIsolati on(WSJdbcConnection.java:3707) at com.ibm.ws.recoverylog.custom.jdbc.impl.SQLMultiScopeRecoveryLog .prepareConnectionForBatch(SQLMultiScopeRecoveryLog.java:3652) at com.ibm.ws.recoverylog.custom.jdbc.impl.SQLMultiScopeRecoveryLog .internalForceSections(SQLMultiScopeRecoveryLog.java:2107) at com.ibm.ws.recoverylog.custom.jdbc.impl.SQLMultiScopeRecoveryLog .forceSections(SQLMultiScopeRecoveryLog.java:2053) at com.ibm.ws.recoverylog.custom.jdbc.impl.SQLRecoverableUnitImpl.f orceSections(SQLRecoverableUnitImpl.java:599) at com.ibm.ws.recoverylog.custom.jdbc.impl.SQLRecoverableUnitImpl.f orceSections(SQLRecoverableUnitImpl.java:537) at com.ibm.tx.jta.impl.RecoveryManager.updateTranLogServiceData(Rec overyManager.java:1205) at com.ibm.tx.jta.impl.RecoveryManager.run(RecoveryManager.java:216 6) at java.lang.Thread.run(Thread.java:809)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere Application Server users that * * have configured the transaction service to * * store its logs in an Oracle database. * **************************************************************** * PROBLEM DESCRIPTION: CWRLS0009E occurs due to failure * * Exception calling * * setTransactionIsolation on a JDBC * * connection. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PI65127 introduced a change that was targeted at DB2 but, in error, affected all supported database platforms.
Problem conclusion
The recovery log component was modified so that the correct initilization is performed depending on database type. The fix for this APAR is currently targeted for inclusion in WebSphere Application Server fix packs 8.0.0.13, 8.5.5.11 and 9.0.0.3 and WebSphere Application Server Liberty fix pack 17.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
PI72136
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-11-10
Closed date
2016-12-12
Last modified date
2016-12-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
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R800 PSY
UP
R850 PSY
UP
R900 PSY
UP
Document Information
Modified date:
04 May 2022