3 months ago
We call out to an external DB from our Java Spring app. We typically do not have issues but beginning this morning at 8:47AM CST we began seeing transient issues related to connection timeouts. Are there any network issues currently at Railway?
caused by:
org.springframework.dao.DataAccessResourceFailureException: Unable to acquire JDBC Connection [HikariPool-1 - Connection is not available, request timed out after 30000ms.] [n/a] -> Caused by: org.hibernate.exception.JDBCConnectionException: Unable to acquire JDBC Connection [HikariPool-1 - Connection is not available, request timed out after 30000ms.] [n/a] -> Caused by: java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30000ms.
1 Replies
3 months ago
Hello,
There are no ongoing incidents on our end. You can always check status.railway.com for real-time updates. Since you're connecting to an external database, I'd recommend reaching out to that provider to see if they experienced any issues around that time.
That said, the HikariPool timeout you're seeing typically means your connection pool is exhausted, all connections are in use, and new requests are waiting longer than the 30-second timeout. This can happen if connections aren't appropriately released, if there's a sudden spike in traffic, or if the external database is responding slowly. It might be worth reviewing your pool configuration (max pool size, connection timeout, idle timeout) and checking whether traffic patterns changed this morning.
Best,
Brody
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 3 months ago