com.sun.appserv.connectors.internal.api.PoolingException: In-use connections equal max-pool-size and expired max-wai >>> t-time. Cannot allocate more connections.|#] Caused by: java.sql.SQLException: Error in allocating a connection. Cause: In-use connections equal max-pool-size and expired max-wait-time. Cannot allocate more connections.

Oracle Community | pgiblox | 6 years ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    CORBA killing transaction and jdbc connection leak [GF3.0.1]

    Oracle Community | 6 years ago | pgiblox
    com.sun.appserv.connectors.internal.api.PoolingException: In-use connections equal max-pool-size and expired max-wai >>> t-time. Cannot allocate more connections.|#] Caused by: java.sql.SQLException: Error in allocating a connection. Cause: In-use connections equal max-pool-size and expired max-wait-time. Cannot allocate more connections.

    Root Cause Analysis

    1. com.sun.appserv.connectors.internal.api.PoolingException

      In-use connections equal max-pool-size and expired max-wai >>> t-time. Cannot allocate more connections.|#] Caused by: java.sql.SQLException: Error in allocating a connection. Cause: In-use connections equal max-pool-size and expired max-wait-time. Cannot allocate more connections.

      at com.sun.gjc.spi.base.DataSource.getConnection()
    2. Embedded GlassFish Web
      DataSource.getConnection
      1. com.sun.gjc.spi.base.DataSource.getConnection(DataSource.java:112)
      1 frame
    3. Hibernate EJB
      InjectedDataSourceConnectionProvider.getConnection
      1. org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider.getConnection(InjectedDataSourceConnectionProvider.java:71)
      1 frame
    4. Hibernate
      ConnectionManager.openConnection
      1. org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:446)
      1 frame