Getting error while requesting for multiple users at a time in SailPoint IIQ 8.4

IdentityIQ (IIQ) IIQ Discussion and Questions
, ,
1

Which IIQ version are you inquiring about?

We are using IIQ 8.4

Please share any images or screenshots, if relevant.

image
image1147×222 22.9 KB

Share all details about your problem, including any error messages you may have received.

When we are requesting for Role (Bundle) from manage my access for many users (6+) then it is taking time (1 min+) and throwing SailPoint OOTB error as shown in above image although the request is getting submitted successfully. And we are using Load balancer for access requests. so, is there any timeout from Sailpoint iiq for the request to get submitted? or it is a Load balancer issue? Attached the log also. The main error is : Caused by: java.net.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

IIQ_Error_Multiple_Users_Bundle.txt (22.2 KB)

2

Hi @KUjjwal,

see the logs for keeping more info. The error si could be not correlated with LB.

3

Hi @enistri_devo here is the log
IIQ_Error_Multiple_Users_Bundle.txt (22.2 KB)

getting Caused by: java.net.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

4

Hi @KUjjwal,

It seems to be time-out issue only. Have you tried running this use-case with different person (request submitter) and different browser?

If possible, can you enable the developer tool in your browser during request submission and check the logs for more insight?

Thank

1 Like
5

Thanks, the problem could be depeds on firewall between UI/Task and Sailpoint DB or a firewall before the target system or on target system.SP dont want a FW between UI/Task and DB.

You can try to increase the timeouts on sailpoint side; you can modify the server.xml on HOME_TOMCAT/conf folder:

<Connector port="8080" protocol="HTTP/1.1"
           connectionTimeout="60000"
           redirectPort="8443" />

<Connector port="8080" protocol="HTTP/1.1"
           keepAliveTimeout="60000"
           maxKeepAliveRequests="100" />

If the problem continue, check the network performance between SP and target systems.

2 Likes
6

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