weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: IO Error: Connection reset

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 2975456, 1 year ago
weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: IO Error: Connection reset
via oracle.com by Unknown author, 1 year ago
weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: IO Error: The Network Adapter could not establish the connection
via hivmr.com by Unknown author, 1 year ago
weblogic.common.resourcepool.ResourceDeadException: Pool p13nDataSource has been disabled because of hanging connection tests, cannot allocate resources to applications. We waited 10018 milliseconds. A typical test has been taking 4
via Oracle Community by 574388, 1 year ago
weblogic.common.resourcepool.ResourceDeadException: Pool p13nDataSource has been disabled because of hanging connection tests, cannot allocate resources to applications. We waited 10018 milliseconds. A typical test has been taking 4
via hivmr.com by Unknown author, 1 year ago
weblogic.common.resourcepool.ResourceDeadException: Pool p13nDataSource has been disabled because of hanging connection tests, cannot allocate resources to applications. We waited 10018 milliseconds. A typical test has been taking 4
via Oracle Community by Maahjoor, 1 year ago
weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: IO Error: Connection reset
weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: IO Error: Connection reset
at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:250)
at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:352)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:369)
at com.sigmadynamics.server.SDDataSource.getConnection(SDDataSource.java:85)
at com.sigmadynamics.server.DataServices.DatabaseProvider.DatabaseProvider.getConnection(DatabaseProvider.java:181)
at com.sigmadynamics.server.DataServices.DatabaseProvider.BatchUpdater.synchronousOperation(BatchUpdater.java:504)
at com.sigmadynamics.server.DataServices.DatabaseProvider.BatchUpdater.operation(BatchUpdater.java:258)
at com.sigmadynamics.server.DataServices.DatabaseProvider.TableDeleterImpl.delete(TableDeleterImpl.java:51)
at com.sigmadynamics.cluster.persist.TopologyDatabaseStorage.retainNewest(TopologyDatabaseStorage.java:355)
at com.sigmadynamics.server.kernel.RemoteInstanceDatabaseStorage.retainNewest(RemoteInstanceDatabaseStorage.java:139)
at com.sigmadynamics.cluster.RTDClusterRegistry.coordinatorDuties(RTDClusterRegistry.java:486)
at com.sigmadynamics.cluster.RTDClusterRegistry.updateFromRemotes(RTDClusterRegistry.java:394)
at com.sigmadynamics.cluster.RTDClusterRegistry.run(RTDClusterRegistry.java:249)
at com.sigmadynamics.server.kernel.RTDServerTimerAndJobRunner$JobCatcher.run(RTDServerTimerAndJobRunner.java:181)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
at com.sigmadynamics.server.kernel.RTDServerTimerAndJobRunner$1$1.run(RTDServerTimerAndJobRunner.java:131)

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 1 year ago

Know the solutions? Share your knowledge to help other developers to debug faster.