sailpoint.connector.ConnectorException: java.lang.InterruptedException: Timeout waiting for response to message

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

We are having a jdbc connector with jdbc provisioning rule to delete users whenever disable operation is triggered .however when ever the disable operation is triggered it fails at sailpoint but in the db the user is deleted.We have also tried to increase timeout but it does not work.
image

2

@colin_mckibben can you suggest why this is happening

3

I’m not an expert on the JDBC connector but it sounds like sailpoint sends the delete operation to the database but the database isn’t responding with a success code. What database are you connecting to?

4

oracle database we are using

5

Hi @schattopadhy

Welcome to SailPoint developer community.

How about other operations, are you facing this exception only for delete operation ?

Thanks
Krish

6

Did you try setting “provisioningTimeout” and “timeout” to a big number like 360 and then verify?

7

only for delete operation not for others

8

yes i have setup till 240 but same response

9

It may have something to do with the version of oracle database you are using and how that version responds to the JDBC connector. It may be responding in a way the connector is not expecting, which might be a bug. If you haven’t already, please open a support ticket so our support team can investigate.

10

Hi @schattopadhy ,

Try enabling the log in your provisioning rule to see the control is returned ontime after it deletes the records. Hope you are setting the plan status properly in your rule.

Regards,
Karthi

11

Shantanu-

The delete operation can be time consuming on the database side if the table contains a huge number of rows. The health of the indexes on that table can also be a factor. Your DBA of this remote JDBC application can run an Oracle AWR report for the period when the delete operation occurs and see if the delete statement is one of the longer-running operations. The AWR report is also helpful because the DBA can then retrieve the exact SQL statement in play and get an explain plan to see what the bottleneck might be. Tracing from the SailPoint side is really difficult to retrieve the problematic SQL, so I recommend having the DBA try to fish it out using the AWR report.

2 Likes
13

This is not issue with one connector but overall VA issue at least in our org.
We are seeing random timeout for all sources since last 2-3 weeks and support has found out this to be VA issue.
If you are just seeing issue with one source and if it is consistent then it is not VA.

14

@chirag_patel the issue is not for all operation only for delete and yes its coming for most of the jdbc sources we have configured

15

only for delete others are fine

16

Have you tried restarting you VA’s?

17

yes we have but that did not work

18

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.