weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: Could not create pool connection. The DBMS driver exception was: Closed Connection

Oracle Community | 2769563 | 2 years ago
  1. 0

    Understanding the AWR report

    Oracle Community | 2 years ago | 2769563
    weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: Could not create pool connection. The DBMS driver exception was: Closed Connection
  2. 0

    Working with OAM Access Server SDK 11g - Oracle Trainings for Apps & Fusion DBA Oracle Trainings for Apps & Fusion DBA: Oracle Implementation & Training Experts

    onlineappsdba.com | 12 months ago
    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
  3. 0

    Use of CountOfRefreshFailuresTillDisable

    Oracle Community | 1 decade ago | 666705
    weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:Could not create pool connection. The DBMS driver exception was: java.net.NoRouteToHostException: No route to host: connect.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Issue on ADF application session timeout

    Oracle Community | 1 year ago | Ove
    weblogic.jdbc.extensions.ConnectionDeadSQLException: 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
  6. 0

    ADF application that deployed on weblogic 10.3.6 hangs

    Oracle Community | 3 years ago | User495329-OC
    weblogic.jdbc.extensions.ConnectionDeadSQLException: 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

    1 unregistered visitors
    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. weblogic.jdbc.extensions.ConnectionDeadSQLException

      weblogic.common.resourcepool.ResourceDeadException: Could not create pool connection. The DBMS driver exception was: Closed Connection

      at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException()
    2. weblogic.jdbc.common
      JDBCUtil.wrapAndThrowResourceException
      1. weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:249)
      1 frame
    3. weblogic.jdbc.pool
      Driver.connect
      1. weblogic.jdbc.pool.Driver.connect(Driver.java:160)
      1 frame
    4. weblogic.jdbc.jts
      Driver.connect
      1. weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:642)
      2. weblogic.jdbc.jts.Driver.connect(Driver.java:124)
      2 frames
    5. weblogic.jdbc.common
      RmiDataSource.getConnection
      1. weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:338)
      1 frame
    6. com.bci.rms
      DAOUtil.getConnectionFromDataSource
      1. com.bci.rms.ea.common.eautil.dao.DAOUtil.getConnectionFromDataSource(DAOUtil.java:222)
      1 frame