Database Connection Pool Exhausted
All connections in the database connection pool are in use and no new connections can be acquired.
Root Cause
Too many concurrent requests, connection leaks (connections not released), or the pool size is too small for the workload.
How to Fix
Increase the pool size. Fix connection leaks by ensuring connections are always released (use try/finally). Implement connection timeouts.
Quick Summary
Connection pool exhausted, all database connections are in use. Fix connection leaks, increase pool size, and implement connection timeouts. Always release connections in a finally block.
Key Takeaways
- Connection leaks are the most common cause, always release connections in finally blocks
- Increase pool size: max: 20 in your pool configuration
- Set a connection timeout to fail fast instead of hanging
- Monitor pool usage with your database's connection metrics
When to use it
- Connection leak in a request handler
- Traffic spike exceeding pool capacity
- Long-running queries holding connections
Common Mistakes
- Not releasing connections in error paths, always use try/finally or a connection wrapper
- Setting pool size too high, too many connections can overwhelm the database
PoolError Database Connection Pool Exhausted, Frequently Asked
How do I detect connection leaks?
Enable pool logging to see connection acquisition and release. A growing number of active connections that never decreases indicates a leak.
Still having issues?
Check your network logs or use our developer tools to inspect headers, decode tokens, or validate your requests.