JDBC Pool: Refcursor value is invalid on connection release
Daniel Hoppe
this is what I found in our server logs when analyzing a stalled server:
####<Feb 24, 2002 12:12:36 PM CET> <Info> <JDBC Pool oraclePool>
<finstsv2> <finstralserver> <ExecuteThread: '2' for queue: 'default'> <>
<> <000000> <A connection from pool oraclePool was tested during release
with a select count(*) from finstral_WL_POOL_TEST and failed:
>
####<Feb 24, 2002 12:12:36 PM CET> <Info> <JDBC Pool oraclePool>
<finstsv2> <finstralserver> <ExecuteThread: '2' for queue: 'default'> <>
<> <000000> <java.sql.SQLException: Refcursor value is invalid
at
oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:180)
at
oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:222)
at oracle.jdbc.dbaccess.DBError.check_error(DBError.java:944)
at oracle.jdbc.ttc7.TTCStatement.<init>(TTCStatement.java:41)
at oracle.jdbc.ttc7.TTC7Protocol.open(TTC7Protocol.java:475)
at
oracle.jdbc.driver.OracleStatement.<init>(OracleStatement.java:492)
at
oracle.jdbc.driver.OracleConnection.privateCreateStatement(OracleConnect
ion.java:619)
at
oracle.jdbc.driver.OracleConnection.createStatement(OracleConnection.jav
a:513)
at
weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:940)
at
weblogic.common.internal.ResourceAllocator.release(ResourceAllocator.jav
a:782)
at
weblogic.common.internal.ResourceAllocator.release(ResourceAllocator.jav
a:817)
at
weblogic.jdbc.common.internal.ConnectionEnv.destroy(ConnectionEnv.java:5
86)
at
weblogic.jdbc.common.internal.ConnectionEnv.destroy(ConnectionEnv.java:5
48)
at
weblogic.jdbc.jts.Connection.internalClose(Connection.java:661)
at
weblogic.jdbc.jts.Connection.internalRollback(Connection.java:686)
at weblogic.jdbc.jts.Connection.rollback(Connection.java:434)
at
weblogic.transaction.internal.ServerResourceInfo.rollback(ServerResource
Info.java:1236)
at
weblogic.transaction.internal.ServerResourceInfo.rollback(ServerResource
Info.java:555)
at
weblogic.transaction.internal.ServerSCInfo.startRollback(ServerSCInfo.ja
va:370)
at
weblogic.transaction.internal.ServerTransactionImpl.localRollback(Server
TransactionImpl.java:1423)
at
weblogic.transaction.internal.ServerTransactionImpl.globalRollback(Serve
rTransactionImpl.java:2016)
at
weblogic.transaction.internal.TransactionImpl$1.execute(TransactionImpl.
java:1566)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
####<Feb 24, 2002 12:12:36 PM CET> <Info> <JDBC Pool oraclePool>
<finstsv2> <finstralserver> <ExecuteThread: '2' for queue: 'default'> <>
<> <000000> <This connection will now be refreshed.>
Does anyone have a clue what this might be? Our application doesn't make
any use of RefCursors, Stored Functions, ..., just prepared statements
and CMP entity beans.
Thanks for your hints!
Daniel
Sree Bodapati
pool just testing the connection once your app has returned it to the pool,
It will cleaning up a bad connection and retest with a new one. so this
should be ok. This is probably one of those bad connections for which the
test failed and connection pool must has created a new one by discarding
this one.
hth
/
sree
"Daniel Hoppe" <ho...@sitewaerts.de> wrote in message
news:923A7281CDB7D4118A50...@samoa.sitewaerts...