HikariPool-1 - Connection is not available, request timed out after 30000ms
The connection pool was exhausted — all connections were busy for 30 seconds.
Seen on:
Java
Meaning
Long transactions, slow queries, connection leaks (not closed) or a pool too small for the concurrency cause requests to wait and time out.
Common causes
- Connection leaks (connections not returned)
- Slow queries holding connections
- Pool too small for load
- Long @Transactional methods doing network calls
⚡ Quick fix
- Enable leak detection (leakDetectionThreshold)
- Fix slow queries
- Keep transactions short
- Size the pool for your DB’s capacity
Detailed fix by platform
Java
spring.datasource.hikari.leak-detection-threshold=20000
How to diagnose
- Pool — Active vs max connections
- Holders — Which code holds connections longest?
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 2 Oct 2026