Share all details about your problem, including any error messages you may have received.
Hi all, I have an OpenLDAP - Direct application which intermittently gets Exception during aggregation. Reason: java.lang.RuntimeException: sailpoint.connector.ConnectorException: [ ConnectorException ] [ Error details ] [ ConnectorException ] [ Error details ] Failed to aggregate.[ ConnectorException ] [ Error details ] LDAP connection has been closed.
Would like to check if below options can be used to allow aggregation to continue after hitting this error. Anyone has experience trying below solutions?
Adding the error message to retryableErrors key in the aggregation task
you can add the retryable errors as per the sailpoint documentation. please find the below
in addition to this, please check with openldap team on what are the reasons of LDAP connection getting closed. you can ask them to check the access logs at open LDAP side to see if the requests are being closed when you make an aggregation connection from sailpoint or any network issues in between ?
Retryable mechanism
For availing the advantage of some of the logic around retryable situations, add the retryable error messages list
to the attributes map on an application. The retryableErrors entry is a list of strings through which the connector
searches when it receives a message from the managed application. If one of the strings in the entry exists in the
error, the connector attempts to retry the connection. When the configured error string is not a part of the error
message returned from the connector, then IdentityIQ would not attempt a retry.
Here is an example of this entry:
<entry key="retryableErrors"> <value> <List> <String>Server is not operational</String> </List> </value> </entry>
Server is not operational
Precaution: Avoid using error messages which contain a date/time, sequence id, SM packets/messages, and so
on, as these are very specific. Error codes or error message substrings would be good candidates for inclusion
Yes, both approaches you mentioned can help, depending on the root cause:
Adding the error to retryableErrors: This is a common approach for intermittent connection issues. It lets the aggregation automatically retry when this specific LDAP connection error occurs. Make sure to test it with your LDAP environment to avoid endless retries.
Adjusting Java settings: Increasing connection pool size, timeout, or heap can help if the aggregation fails due to resource limits or network latency.
There is one more parameter maxretries= this should help. Please check and try in your non prod environment before implementing in the live environment.
Hello @shijingg Can I know which version of Java is being used here? Previously, I faced the same error while performing aggregation for the OpenLDAP connector. The reason was that the Apache DS (running as the server for this connector) only supports Java 11. After I changed the version from Java 17 to Java 11, it started working.
