weblogic.common.ResourceException: failed to make pool eng23567: javax.naming.NameAlreadyBoundException; remaining name 'weblogic.jdbc.connection Pool.eng23567'

Oracle Community | 3004 | 2 decades ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    Dynamic Connection pool

    Oracle Community | 2 decades ago | 3004
    weblogic.common.ResourceException: failed to make pool eng23567: javax.naming.NameAlreadyBoundException; remaining name 'weblogic.jdbc.connection Pool.eng23567'
  2. 0

    Dynamic Connection pool

    Oracle Community | 2 decades ago | 3004
    weblogic.common.ResourceException: failed to make pool eng23567: javax.naming.NameAlreadyBoundException; remaining name 'weblogic.jdbc.connection Pool.eng23567'
  3. 0

    JDBC connection pool getting killed in Managed Server

    Oracle Community | 2 decades ago | 3004
    weblogic.common.ResourceException: creating Admin MBean on a managed server
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. weblogic.common.ResourceException

      failed to make pool eng23567: javax.naming.NameAlreadyBoundException; remaining name 'weblogic.jdbc.connection Pool.eng23567'

      at weblogic.jdbc.common.internal.ConnectionPool.startup()
    2. weblogic.jdbc.common
      ConnectionPool.createPool
      1. weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:330)
      2. weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:386)
      3. weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:368)
      3 frames
    3. com.connect
      TableBeanEOImpl.getTMDetails
      1. com.connect.TableBean.getTMDetails(TableBean.java:75)
      2. com.connect.TableBeanEOImpl.getTMDetails(TableBeanEOImpl.java:56)
      2 frames