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

Dismiss

ResourceException: None Available

1 view

Skip to first unread message

Jinsong Hu

unread,

May 21, 2002, 4:08:11 PM5/21/02

Hi,

We hit the ResourceException: None Available in weblogic6.0 sp2, actually, we
close the connection correctly, but this problem still exists. Before we hit this
exception, we really have a lot of "transaction aleady rolled back" exceptions, I
guess this cause the resource exception, please see this two exceptions:
(1)
java.sql.SQLException: Transaction 31034:bdb923a07d3c2c91 not active anymore. tx
status = Marked rollback. [Reason = weblogic.transaction.internal.AppSetRollbackOnlyException]
at weblogic.jdbcbase.jts.Driver.getTransaction(Driver.java:235)
at weblogic.jdbcbase.jts.Driver.connect(Driver.java:106)
at java.sql.DriverManager.getConnection(DriverManager.java:517)
at java.sql.DriverManager.getConnection(DriverManager.java:199)
at glog.util.jdbc.noserver.T2Connection.getConnection(T2Connection.java:98)
at glog.util.jdbc.T2SharedConnection$ReferencedConnection.addRef(T2SharedConnection.java:58)
at glog.util.jdbc.T2SharedConnection.open(T2SharedConnection.java:37)
at glog.server.workflow.tender.TenderWorkflow.getTransmissionFromTransaction(TenderWorkflow.java:267)
at glog.server.workflow.tender.ConfirmTransportArrangements.terminate(ConfirmTransportArrangements.java:216)
at glog.server.workflow.Workflow.execute(Workflow.java:82)
at glog.server.workflow.WorkflowSessionBean.execute(WorkflowSessionBean.java:49)
at glog.server.workflow.WorkflowSessionBeanImpl.execute(WorkflowSessionBeanImpl.java:189)
at glog.server.workflow.WorkflowSessionBeanEOImpl.execute(WorkflowSessionBeanEOImpl.java:125)
at glog.server.workflow.WorkflowManager.execute(WorkflowManager.java:217)
at glog.server.workflow.Trigger.trigger(Trigger.java:103)
at glog.util.event.EventQueue.run(EventQueue.java:143)
at java.lang.Thread.run(Thread.java:484)

(2)
(null)/java.sql.SQLException: Pool connect failed: weblogic.common.ResourceException:
None available
java.sql.SQLException: Pool connect failed: weblogic.common.ResourceException: None
available
at weblogic.jdbcbase.pool.Driver.connect(Driver.java:218)
at weblogic.jdbcbase.jts.Driver.getNonTxConnection(Driver.java:303)
at weblogic.jdbcbase.jts.Driver.connect(Driver.java:116)
at java.sql.DriverManager.getConnection(DriverManager.java:517)
at java.sql.DriverManager.getConnection(DriverManager.java:199)
at glog.util.jdbc.noserver.T2Connection.getConnection(T2Connection.java:98)
at glog.server.query.JDBCConnection.open(JDBCFinder.java:505)
at glog.server.query.JDBCFinder.openConnection(JDBCFinder.java:208)
at glog.server.query.JDBCFinder.open(JDBCFinder.java:92)
at glog.server.query.ListRetrieverBean.set(ListRetrieverBean.java:31)
at glog.server.query.ListRetrieverBeanImpl.set(ListRetrieverBeanImpl.java:149)
at glog.server.query.ListRetrieverBeanEOImpl.set(ListRetrieverBeanEOImpl.java:51)
at glog.server.query.ListRetrieverBeanEOImpl_WLSkel.invoke(ListRetrieverBeanEOImpl_WLSkel.java:181)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Is it possible because of the first exception, weblogic does not manage pool
correctly and cause the second exception?

Any comments?

Thanks

0 new messages