Timeout error from UI while VA connects successfully

[SharathPurushotham]

Hi all,

I’m attempting to connect to an Oracle database using a JDBC connector. The connection test from the Virtual Appliance (VA) is successful, so I’m assuming it’s not a firewall-related issue.

However, when I test the connection from the IdentityNow UI, I receive a timeout error. The VA itself appears to be functioning properly, as other sources connected to the same VA are working as expected.

I also tried increasing the connection timeout settings, but it didn’t make any difference.

Has anyone encountered a similar issue, or are there any recommendations on what else I should check?

Thanks in advance!

[Rohit_Sahu]

Hi @SharathPurushotham ,

Once try with the re-enter your username and password in the account–> connection settings.

hope this will work.

Thank You!

[SharathPurushotham]

I have done this as well, I have also updated the IP address directly in the connection string rather than the DNS, that does not work as well.
I have also updated the JAR file by renaming it was not successfully.

I am able to successfully connect in stg environment with the same config fails in production

[sidharth_tarlapally (TARLAPALLY SIDHARTH)]

Ensure the DB allows Sailpoint VA to connect to it .

Connection Issue with the JDBC Source

Hey @rohitmisal45 , This is a generic error . Please ensure the provided password is right . Check if the Database you are trying to access is allowing the external parties to act upon . I can see you are using root user as service account , check with this command if the root has permission on ‘%’ which means ALL : SELECT host FROM mysql.user WHERE user = 'root'; [image] Mysql permissions distinguish by host and ip. Permissions granted for a hostname do not work for an IP and vice ve…

[SharathPurushotham]

Hi Sidharth, I have tried this, and the service account has the access to read data from the database. And I am using the same service account from stg which is able to connect to the database through the UI.

[sidharth_tarlapally (TARLAPALLY SIDHARTH)]

@SharathPurushotham

So the same configuration and connection is happening on stg and not on dev/prod?

[SharathPurushotham]

Yes, the same configuration is happening from STG and not from prod.

[Chaithu9110 (CHAITHANYA M)]

look va logs for clues
/opt/sailpoint/va/logs/connector/

2.Reset the database password with a simple test value, update the source config, and retest.

[Snaren951 (Narendra Siriki)]

@SharathPurushotham
Hi Sharath,

I come across a similar issue when setting the JDBC connector to connect to the DB installed in my local machine from the VM.

The VA status =connected means that it is successfully connected & paired with your ISC Cloud Tenant. It doesn’t guarantee the connection to DB from the VA.

You have to make sure that the VA can connect to the Local machine to access the DB, in my case , I used Virtual Box to set up the VM, and in network setting I used ‘NAT’, and that caused the issue in the first place. Later when I changed the Network settings to use ‘Bridged Mode’, it was able to connect to the local machine and the DB. Also, make sure to use the IP address of the localhost (example: 192.134.2.1:3306) instead of localhost:3306

[ManvithaNalabolu06 (Manvitha Nalabolu)]

@SharathPurushotham

I’m attempting to connect to an Oracle database using a JDBC connector. The connection test from the Virtual Appliance (VA) is successful, so I’m assuming it’s not a firewall-related issue.

However, when I test the connection from the IdentityNow UI, I receive a timeout error. The VA itself appears to be functioning properly, as other sources connected to the same VA are working as expected.

I also tried increasing the connection timeout settings, but it didn’t make any difference.

Has anyone encountered a similar issue, or are there any recommendations on what else I should check?

Thanks in advance!

The VA “Test Connection” only checks basic network reachability, not full JDBC connectivity — so it can succeed while the IdentityNow UI test fails. Its due to incorrect JDBC URL format, missing or incompatible Oracle JDBC driver, or authentication problems. Ensure the VA has enough resources if multiple sources are running.