Suneep Nair
07/22/2025, 5:51 PM2025-07-22 17:48:54,618 [health-executor-thread-3] ERROR i.a.d.s.i.j.HealthCheckServiceJooqImpl(healthCheck):40 - Health check error:
Caused by: java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30000ms (total=0, active=0, idle=0, waiting=3)
kapa.ai
07/22/2025, 5:51 PMjava.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30000ms (total=0, active=0, idle=0, waiting=3)
means that all connections in the pool are in use or unavailable, and after waiting 30 seconds, no connection became available. The details (total=0, active=0, idle=0, waiting=3)
show that there are no available connections in the pool, and three threads are waiting for a connection. Common causes for this error in Airbyte include: - The database server is not reachable (network issues, wrong hostname/port, or the server is down). - The database does not exist or is not initialized. - Incorrect authentication credentials. - The database is overloaded or not accepting new connections. - The connection pool is misconfigured or exhausted. For example, similar errors have been reported when the target database does not exist, the database server is refusing connections, or the credentials are incorrect. In these cases, Airbyte cannot establish a connection, resulting in a timeout from the HikariCP pool [[Unable to install Airbyte locally - Unable to connect to the database](https://github.com/airbytehq/airbyte/issues/45456)] [[Failed to connect to external postgres DB](https://discuss.airbyte.io/t/1264)]. To resolve this, check your database configuration, ensure the database is running and accessible, and verify your credentials and network settings.