From 3634d7a93edb8b4b7b83a0fe2475194fbbdba691 Mon Sep 17 00:00:00 2001 From: Nico Piel Date: Mon, 25 May 2026 23:03:44 +0200 Subject: [PATCH] fix: set HikariCP connectionTimeout to 30s Previously connectionTimeout was set to 0, which HikariCP interprets as wait indefinitely for a pool connection. Under any connection pressure this causes caller threads to block forever, silently starving the application with no way to detect or recover from the condition. Change the value to 30000 ms (30 seconds), which matches the HikariCP default. Callers will now receive a SQLException after 30 s instead of hanging, surfacing pool starvation quickly and allowing the application to fail fast and recover. Signed-off-by: Nico Piel --- .../connect/donkey/server/data/jdbc/HikariConnectionPool.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/donkey/src/main/java/com/mirth/connect/donkey/server/data/jdbc/HikariConnectionPool.java b/donkey/src/main/java/com/mirth/connect/donkey/server/data/jdbc/HikariConnectionPool.java index 54bc41ad6c..ed6848acc0 100644 --- a/donkey/src/main/java/com/mirth/connect/donkey/server/data/jdbc/HikariConnectionPool.java +++ b/donkey/src/main/java/com/mirth/connect/donkey/server/data/jdbc/HikariConnectionPool.java @@ -28,7 +28,7 @@ public HikariConnectionPool(String driver, String url, String username, String p dataSource.setJdbcUrl(url); dataSource.setUsername(username); dataSource.setPassword(password); - dataSource.setConnectionTimeout(0); + dataSource.setConnectionTimeout(30000); dataSource.setAutoCommit(false); dataSource.setMaximumPoolSize(maxConnections); dataSource.setMinimumIdle(0);