Fixes are available
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
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.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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
An ORA-00001 error occurs when a multi-row schema configuration is used for session persistence on an Oracle database. java.sql.BatchUpdateException: ORA-00001: unique constraint (SESS_TECH.SESS_INDEX) violated at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePr eparedStatement.java:17660) at oracle.jdbc.driver.OracleStatementWrapper.executeBatch(OracleSta tementWrapper.java:771) at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteBatc h(WSJdbcPreparedStatement.java:1037) at com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.executeBatch(WSJdbcSta tement.java:843) at com.ibm.ws.session.store.db.DatabaseHashMapMR.handlePropertyHits (DatabaseHashMapMR.java:480) at com.ibm.ws.session.store.db.DatabaseHashMap.persistSession(Datab aseHashMap.java:2125) at com.ibm.ws.session.store.common.BackedHashMap.updateSession(Back edHashMap.java:469) at com.ibm.ws.session.store.common.BackedHashMap.put(BackedHashMap. java:543) at com.ibm.ws.session.store.common.BackedSession.flush(BackedSessio n.java:239) at com.ibm.ws.session.store.common.BackedSession.flush(BackedSessio n.java:224) at com.ibm.ws.session.EOSSessionStorer.storeSession(EOSSessionStore r.java:50) at com.ibm.ws.session.SessionManager.releaseSession(SessionManager. java:523) at com.ibm.ws.session.SessionContext.sessionPostInvoke(SessionConte xt.java:658) at com.ibm.ws.webcontainer.srt.SRTRequestContext.finish(SRTRequestC ontext.java:135) at com.ibm.ws.webcontainer.srt.SRTServletRequest.finish(SRTServletR equest.java:2600) at com.ibm.ws.webcontainer.srt.SRTConnectionContext.finishConnectio n(SRTConnectionContext.java:91) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer. java:1084) at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContai ner.java:1662) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLin k.java:200) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscr imination(HttpInboundLink.java:459) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRe quest(HttpInboundLink.java:526) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequ est(HttpInboundLink.java:312) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complet e(HttpICLReadCallback.java:88) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureComp leted(AioReadCompletionListener.java:175) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyn cFuture.java:217) at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncC hannelFuture.java:161) at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHand ler.java:775) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1862)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server * * V8.5.5 customers using multi-row schema * * configuration for database session * * persistence on an Oracle database. * **************************************************************** * PROBLEM DESCRIPTION: The session manager may fail to use * * an Oracle database for session * * persistence when using a multi-row * * configuration. * **************************************************************** * RECOMMENDATION: * **************************************************************** On a batch update, session manager attempts to use the getParameterMetaData() method from a JDBC PreparedStatement as part of update processing. Calling this method results in a java.sql.SQLException. Additionally, when a batch update succeeds, the Oracle jdbc driver returns a success code of -2 which is different than other JDBC drivers.
Problem conclusion
Changes were made to the session manager code to account for the behavior of the Oracle JDBC driver. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.2. 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
PM99783
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-10-23
Closed date
2014-01-28
Last modified date
2014-01-28
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:
28 April 2022