Troubleshooting
Problem
This error is the result of a JDBC connection issue between Data Collector and the database specified in the JDBC Query stage. This problem is caused by a few issues, including:
Network latency issues.
The database has gone down.
Symptom
When running a pipeline with the 'JDBC Query Executor stage, the following error message is displayed:
RUNNING_ERROR: QUERY_EXECUTOR_002 - Can't open connection: HikariPool-20 - Connection is not available, request timed out after 30001ms.
Resolving The Problem
Ensure that the database is both running and accepting connections.
In the case of network latency, further investigation is required in order to determine the root cause. A temporary solution, outlined below, is available to help remediate the issue.
Using the UI, navigate to the pipeline/job experiencing issues.
Select the JDBC Query stage > Configuration > Advanced , then find the setting for Connection Timeout (Seconds).
By default, this value is set to ${30 * SECONDS}. In this case, increase this value to ${60 * SECONDS} in order to account for latency issues.
Save your changes, then test the pipeline again to check if the error is still present.
NOTE: Increasing the timeout gives the database more time to respond, which can help if latency is intermittent or if the database is experiencing high load. However, this workaround will not be applicable in cases where the network connection to the database is down, or when a firewall is blocking the traffic.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
15 March 2025
UID
ibm17186091