weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: IO Error: Socket read timed out

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

Samebug tips

Do you know how to solve this issue? Write a tip to help other users and build your expert profile.

Solutions on the web

via identityincloud.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: Socket read timed out
via Oracle Community by 666705, 1 year ago
weblogic.common.resourcepool.ResourceDeadException: 0:Could not create pool connection. The DBMS driver exception was: java.net.NoRouteToHostException: No route to host: connect.
via Oracle Community by 2769563, 1 year ago
weblogic.common.resourcepool.ResourceDeadException: Could not create pool connection. The DBMS driver exception was: Closed Connection
via Oracle Community by User495329-OC, 1 year ago
weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Listener refused the connection with the following error: ORA-12519, TNS:no appropriate service handler found
via onlineappsdba.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: Socket read timed out
via Oracle Community by Ove, 1 year ago
weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: IO Error: Got minus one from a read call
weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: IO Error: Socket read timed out
at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:250)
at weblogic.jdbc.pool.Driver.connect(Driver.java:142)
at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:658)
at weblogic.jdbc.jts.Driver.connect(Driver.java:127)
at weblogic.jdbc.common.internal.RmiDataSource.getConnectionInternal(RmiDataSource.java:533)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:498)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:491)
at oracle.security.idaas.common.persistence.jdbc.JDBCManager.getConnection(JDBCManager.java:83)
at oracle.security.idaas.common.config.mbeans.persistence.JAXBXmlDBPersistenceManagerImpl.registerDatabaseListener(JAXBXmlDBPersistenceManagerImpl.java:168)
at oracle.security.idaas.common.config.mbeans.rp.RPMXBeanImpl$1.objectAdded(RPMXBeanImpl.java:561)
at weblogic.jndi.internal.NotifyEventListeners.handleNamespaceChangeListener(NotifyEventListeners.java:52)
at weblogic.jndi.internal.NotifyEventListeners.notifyListeners(NotifyEventListeners.java:36)
at weblogic.jndi.internal.BasicNamingNode$2.run(BasicNamingNode.java:1326)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 1 year ago

Write tip

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