Unable to get a connection from pool

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Unable to get a connection from pool

greenbean
Two of our servers have suddenly run in to issues with “unable to get a connection from pool” errors when pooling JDBC resources (Postgres and Oracle on one machine, just Oracle on the other).  The problem appeared on two machines within the same day.  A problem like this has not appeared in the past.  Do you have any ideas as to why this would happen?
 
It does not look like it is hitting any DB connection limits.  The pool sizes are set to a max of 400.  The log entry in the second and third examples below says that it could not get a connection, but there are still some available.
 
 
2011-07-21 15:54:49,367 (737072696E672D62746D000001314D680A97000150C2) ERROR [org.hibernate.util.JDBCExceptionReporter] (ThreadPoolExecutor-0) unable to get a connection from pool of a PoolingDataSource containing an XAPool of resource oracle with 57 connection(s) (0 still available)
---------------------------------------------------------------------------------------------------------------
011-07-21 14:09:16,023 (737072696E672D62746D000001314D0766EE00143256) ERROR [org.hibernate.util.JDBCExceptionReporter] (http-0.0.0.0-8080-260) unable to get a connection from pool of a PoolingDataSource containing an XAPool of resource postgres with 372 connection(s) (1 still available)
---------------------------------------------------------------------------------------------------------------
2011-07-21 16:34:27,205 (737072696E672D62746D000001314D8C53010001B531) ERROR [org.hibernate.util.JDBCExceptionReporter] (ThreadPoolExecutor-6) unable to get a connection from pool of a PoolingDataSource containing an XAPool of resource oracle with 102 connection(s) (2 still available)
 
Reply | Threaded
Open this post in threaded view
|

Re: Unable to get a connection from pool

snicoll
In BTM's pool yes (at least the two last examples) but maybe not on the server itself. And the fact you hare having the issue on different systems make me wonder about the database.

S.

On Thu, Jul 21, 2011 at 10:18 PM, Urciolo, Kevin J (IS) <[hidden email]> wrote:
Two of our servers have suddenly run in to issues with “unable to get a connection from pool” errors when pooling JDBC resources (Postgres and Oracle on one machine, just Oracle on the other).  The problem appeared on two machines within the same day.  A problem like this has not appeared in the past.  Do you have any ideas as to why this would happen?
 
It does not look like it is hitting any DB connection limits.  The pool sizes are set to a max of 400.  The log entry in the second and third examples below says that it could not get a connection, but there are still some available.
 
 
2011-07-21 15:54:49,367 (737072696E672D62746D000001314D680A97000150C2) ERROR [org.hibernate.util.JDBCExceptionReporter] (ThreadPoolExecutor-0) unable to get a connection from pool of a PoolingDataSource containing an XAPool of resource oracle with 57 connection(s) (0 still available)
---------------------------------------------------------------------------------------------------------------
011-07-21 14:09:16,023 (737072696E672D62746D000001314D0766EE00143256) ERROR [org.hibernate.util.JDBCExceptionReporter] (http-0.0.0.0-8080-260) unable to get a connection from pool of a PoolingDataSource containing an XAPool of resource postgres with 372 connection(s) (1 still available)
---------------------------------------------------------------------------------------------------------------
2011-07-21 16:34:27,205 (737072696E672D62746D000001314D8C53010001B531) ERROR [org.hibernate.util.JDBCExceptionReporter] (ThreadPoolExecutor-6) unable to get a connection from pool of a PoolingDataSource containing an XAPool of resource oracle with 102 connection(s) (2 still available)
 

Reply | Threaded
Open this post in threaded view
|

Re: Unable to get a connection from pool

Ludovic Orban-2
If you configured all your pools to contain up to 400 connections, it could be that the DB server refused opening new connections. The full stack trace would help acknowledging this is the problem.

Without further evidence, I'm inclined to agree with Stephane and blame that on your database lacking resources.

2011/7/22 Stephane Nicoll <[hidden email]>
In BTM's pool yes (at least the two last examples) but maybe not on the server itself. And the fact you hare having the issue on different systems make me wonder about the database.

S.


On Thu, Jul 21, 2011 at 10:18 PM, Urciolo, Kevin J (IS) <[hidden email]> wrote:
Two of our servers have suddenly run in to issues with “unable to get a connection from pool” errors when pooling JDBC resources (Postgres and Oracle on one machine, just Oracle on the other).  The problem appeared on two machines within the same day.  A problem like this has not appeared in the past.  Do you have any ideas as to why this would happen?
 
It does not look like it is hitting any DB connection limits.  The pool sizes are set to a max of 400.  The log entry in the second and third examples below says that it could not get a connection, but there are still some available.
 
 
2011-07-21 15:54:49,367 (737072696E672D62746D000001314D680A97000150C2) ERROR [org.hibernate.util.JDBCExceptionReporter] (ThreadPoolExecutor-0) unable to get a connection from pool of a PoolingDataSource containing an XAPool of resource oracle with 57 connection(s) (0 still available)
---------------------------------------------------------------------------------------------------------------
011-07-21 14:09:16,023 (737072696E672D62746D000001314D0766EE00143256) ERROR [org.hibernate.util.JDBCExceptionReporter] (http-0.0.0.0-8080-260) unable to get a connection from pool of a PoolingDataSource containing an XAPool of resource postgres with 372 connection(s) (1 still available)
---------------------------------------------------------------------------------------------------------------
2011-07-21 16:34:27,205 (737072696E672D62746D000001314D8C53010001B531) ERROR [org.hibernate.util.JDBCExceptionReporter] (ThreadPoolExecutor-6) unable to get a connection from pool of a PoolingDataSource containing an XAPool of resource oracle with 102 connection(s) (2 still available)