JDBC MySQL Connector – Timeout after 15s despite

I am trying to onboard MySQL DB in SailPoint ISC. I have the port configured, and the test connection is working successfully. However, I am still getting a timeout exception error.

Could you please guide me on how to fix this issue?

Hello Sachin. The 15-second Timeout waiting for response to message 0 from client makes me check the VA/CCG first rather than increasing the JDBC timeout.

Please confirm:

  • Under Admin → Connections → Virtual Appliances, does the VA show Connected and the process status under VA Components show OK?
  • While running Test Connection, what error appears in:
/home/sailpoint/log/ccg.log
  • What are you using for the Test Connection SQL Query and MySQL JDBC driver class?

For the query, try:

SELECT 1

with no semicolon, and confirm the MySQL Connector/J driver class is:

com.mysql.cj.jdbc.Driver

If you can share the relevant ccg.log error from the same Test Connection attempt, that should tell us whether the issue is with the VA/CCG or the JDBC connection to MySQL.

Hi @sachink4

Please verify the following items in your tenant:

  1. Check if VA is running fine.
  2. If VA is running fine and showing as connected, then verify if the CCG is up and running or not. You can execute the command below to verify theat:
sudo docker ps

From the output of this command, verify if the ccg is showing as one row or not.
3. Otherwise, from the VA Cluster, check if the CCG Cluster version is showing up or not.
4. If everything looks good from VA end, then try to increase the timeout period of your source. .

are you getting this during accounts aggregation? try to limit number of records to aggregate for testing. if it works, then add/increase timeout accordingly.

Hi @sachink4
First check the VA/CCG connectivity and ccg.log during the same test.

Also verify the MySQL JDBC driver (com.mysql.cj.jdbc.Driver) and try a simple query such as:

SELECT 1;

If VA/CCG is healthy, check connectivity from the VA to the MySQL host/port and review the CCG logs for the exact failure. If the connection works but aggregation is timing out, then check the query/record volume and timeout configuration.