How does a connection pool become corrupted? And is there a way to tell? If it is corrupt would be better to create a connection pool? I am using c3p0.

what do you mean with "corrupted"?

When there's a problem, it will usually show up in the logs. Maybe you're out of cursors? Maybe your proxies have timed out the connection through the firewall, but the server is still trying to use those same ports? Maybe it's just bad code in your apps that is making it look like a connection pool problem. Dig deeper, and post with more details. That might give us some focus.

-Cameron McKenzie

I'm having an issue with a client's site. About 12:00 am their database does a backup and all the hibernate connections time out. The next morning when the client tries to connect the database, the application crashes because their are no connections left and the pool never tries to make new connections. I am thinking the pool is getting corrupt, because the connections are timing out.

Here is some of logging from the server

2009-Aug-17 07:16:01:371 ManagerImpl.logErrorEx():233 ERROR - Cannot get a connection, pool exhausted

2009-Aug-18 08:08:39:828 com.mchange.v2.c3p0.stmt.GooGooStatementCache.checkinAll():297 DEBUG - checkinAll(): com.mchange.v2.c3p0.stmt.GlobalMaxOnlyStatementCache stats -- total size: 0; checked out: 0; num connections: 0; num keys: 0
2009-Aug-18 08:08:39:828 com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.acquireResource():217 DEBUG - com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager@108e246.acquireResource() returning.
2009-Aug-18 08:08:39:828 com.mchange.v2.resourcepool.BasicResourcePool.trace():1644 DEBUG - trace com.mchange.v2.resourcepool.BasicResourcePool@108e25d [managed: 10, unused: 10, excluded: 0] (e.g. com.mchange.v2.c3p0.impl.NewPooledConnection@fb438e)