Test Table in WebLogic console
0 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   Anonymous
Posted On:   Thursday, April 15, 2004 09:08 AM

I'm encountering an error which I haven't encountered before in our production environment. The settings in the console for the connection pool txIIS are the same as they were in testing, only the db instance is different - the test table is called dual and the test reserved connections is checked. But when I start up the managed server, I keep getting this error. I can open a sql plus session and successfully query the dual table, but the exact same connection properties are not allowing the query to find the dual table in the console. Any ideas? ####Apr 14, 2004 5:30:44 PM CDT - Info - JDBC Pool txIIS - ExecuteThread: '11' for queue: 'default' - A connection from    More>>

I'm encountering an error which I haven't encountered before in our production environment. The

settings in the console for the connection pool txIIS are the same as they were in testing, only the db

instance is different - the test table is called dual and the test reserved connections is checked. But

when I start up the managed server, I keep getting this error. I can open a sql plus session and

successfully query the dual table, but the exact same connection properties are not allowing the query to

find the dual table in the console. Any ideas?



####Apr 14, 2004 5:30:44 PM CDT - Info - JDBC Pool txIIS - ExecuteThread: '11' for queue: 'default' - A

connection from pool txIIS was tested during reserve with a select count(*) from dual and failed:

####Apr 14, 2004 5:30:44 PM CDT - Info - JDBC Pool txIIS -ExecuteThread: '11' for queue: 'default' -

oracle.jdbc.xa.OracleXAException
at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:483)
at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:190)
at weblogic.jdbc.jta.VendorXAResource.start(VendorXAResource.java:41)
at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:961)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:533)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:400)
at weblogic.common.internal.ResourceAllocator.reserveWaitSecs(ResourceAllocator.java:390)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:163)
at weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.java:117)
at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1136)
at weblogic.jdbc.jta.DataSource.recover(DataSource.java:868)
at weblogic.transaction.internal.ServerResourceInfo.recover(ServerResourceInfo.java:838)
at weblogic.transaction.internal.ServerSCInfo.recover(ServerSCInfo.java:283)
at weblogic.transaction.internal.ResourceDescriptor.getXidsToBeRolledBack(ResourceDescrip
tor.java:1112)
at weblogic.transaction.internal.ResourceDescriptor.recover(ResourceDescriptor.java:1046)
at weblogic.transaction.internal.ResourceDescriptor.access$9(ResourceDescriptor.java:1029)
at weblogic.transaction.internal.ResourceDescriptor$1.execute(ResourceDescriptor.java:770)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

   <<Less
About | Sitemap | Contact