Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Websphere session persistence gets "protocol violation" using oracle jdbc driver

3 views
Skip to first unread message

Chinmay

unread,
May 28, 2003, 1:25:30 PM5/28/03
to
Hi,

We use oracle (8.1.7) as the session persistence database for our
websphere 3.5.4 application server. After 15 min of running a stress
test, we get the foll. exception. Any idea whats going wrong?

thanks,

Chinmay

java.sql.SQLException: Protocol
violation
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.<init>(Throwable.java:94)
at java.lang.Exception.<init>(Exception.java:42)
at java.sql.SQLException.<init>(SQLException.java:43)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:156)
at oracle.jdbc.dbaccess.DBError.check_error(DBError.java:803)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:549)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1311)
at oracle.jdbc.ttc7.TTC7Protocol.executeFetch(TTC7Protocol.java:661)
at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:1320)
at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1232)
at oracle.jdbc.driver.OracleStatement.doExecuteWithBatch(OracleStatement.java:1353)
at oracle.jdbc.driver.OracleStatement.doExecute(OracleStatement.java:1760)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1805)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:320)
at com.ibm.ejs.cm.cache.CachedStatement.executeUpdate(CachedStatement.java:314)
at com.ibm.ejs.cm.proxy.PreparedStatementProxy.executeUpdate(PreparedStatementProxy.java:235)
at com.ibm.servlet.personalization.sessiontracking.BackedHashtable.ejbStore(BackedHashtable.java:2564)
at com.ibm.servlet.personalization.sessiontracking.BackedHashtable.storeSession(BackedHashtable.java:2272)
at com.ibm.servlet.personalization.sessiontracking.BackedHashtable.put(BackedHashtable.java:2958)
at com.ibm.servlet.personalization.sessiontracking.DatabaseSessionContext.sync(DatabaseSessionContext.java:112)
at com.ibm.servlet.personalization.sessiontracking.SessionData.releaseSession(SessionData.java:260)
at com.ibm.servlet.engine.srt.SRTSessionAPISupport.finish(SRTSessionAPISupport.java:190)
at com.ibm.servlet.engine.srt.SRTConnectionContext.finishConnection(SRTConnectionContext.java:103)
at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:102)
at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67)
at com.ibm.servlet.engine.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:106)
at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:160)
at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:300)


We also get another exception below the above one in the trace log:

StatementProx E Exception closing statement

com.ibm.ejs.cm.exception.IllegalConnectionUseException: Error:
Connection is being used in a way that violates the architecture
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.<init>(Throwable.java:94)
at java.lang.Exception.<init>(Exception.java:42)
at java.sql.SQLException.<init>(SQLException.java:82)
at com.ibm.ejs.cm.portability.PortableSQLException.<init>(PortableSQLException.java:35)
at com.ibm.ejs.cm.exception.IllegalConnectionUseException.<init>(IllegalConnectionUseException.java:26)
at com.ibm.ejs.cm.proxy.Proxy.close(Proxy.java:154)
at com.ibm.ejs.cm.proxy.StatementProxy.__close(StatementProxy.java:61)
at com.ibm.ejs.cm.proxy.StatementProxy.close(StatementProxy.java:216)
at com.ibm.ejs.cm.proxy.Proxy.close(Proxy.java:76)
at com.ibm.ejs.cm.proxy.ConnectionProxy.close(ConnectionProxy.java:645)
at com.ibm.ejs.cm.proxy.ConnectionProxy.connectionDestroyed(ConnectionProxy.java:97)
at com.ibm.ejs.cm.pool.ConnectO.fireConnectionDestroyed(ConnectO.java:1500)
at com.ibm.ejs.cm.pool.ConnectO.destroy(ConnectO.java:741)
at com.ibm.ejs.cm.pool.ConnectO.translateException(ConnectO.java:1134)
at com.ibm.ejs.cm.proxy.ConnectionProxy.translateException(ConnectionProxy.java:177)
at com.ibm.ejs.cm.proxy.PreparedStatementProxy.translateException(PreparedStatementProxy.java:484)
at com.ibm.ejs.cm.proxy.PreparedStatementProxy.executeUpdate(PreparedStatementProxy.java:238)
at com.ibm.servlet.personalization.sessiontracking.BackedHashtable.ejbStore(BackedHashtable.java:2564)
at com.ibm.servlet.personalization.sessiontracking.BackedHashtable.storeSession(BackedHashtable.java:2272)
at com.ibm.servlet.personalization.sessiontracking.BackedHashtable.put(BackedHashtable.java:2958)
at com.ibm.servlet.personalization.sessiontracking.DatabaseSessionContext.sync(DatabaseSessionContext.java:112)
at com.ibm.servlet.personalization.sessiontracking.SessionData.releaseSession(SessionData.java:260)
at com.ibm.servlet.engine.srt.SRTSessionAPISupport.finish(SRTSessionAPISupport.java:190)
at com.ibm.servlet.engine.srt.SRTConnectionContext.finishConnection(SRTConnectionContext.java:103)
at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:102)
at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67)
at com.ibm.servlet.engine.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:106)
at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:160)
at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:300)

Joseph Weinstein

unread,
May 28, 2003, 1:40:43 PM5/28/03
to Chinmay

Chinmay wrote:

> Hi,
>
> We use oracle (8.1.7) as the session persistence database for our
> websphere 3.5.4 application server. After 15 min of running a stress
> test, we get the foll. exception. Any idea whats going wrong?
>
> thanks,
>
> Chinmay
>
> java.sql.SQLException: Protocol

This is most likely that you are not using the correct/latest appropriate
version of the Oracle driver for your DBMS version.
Joe Weinstein at BEA

0 new messages