# LDAP connection has been closed error during account aggregation **URL:** \ **Category:** IIQ Discussion and Questions\ **Tags:** identityiq, aggregation\ **Created:** [September 9, 2025, 4:49am UTC](https://developer.sailpoint.com/discuss/t/ldap-connection-has-been-closed-error-during-account-aggregation/177743 "2025-09-09T04:49:36Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![shijingg](https://avatars.discourse-cdn.com/v4/letter/s/e9c0ed/32.png) [@shijingg](https://developer.sailpoint.com/discuss/u/shijingg)\ **Post date:** [September 9, 2025, 4:49am UTC](https://developer.sailpoint.com/discuss/t/ldap-connection-has-been-closed-error-during-account-aggregation/177743/1 "2025-09-09T04:49:36Z")
## Which IIQ version are you inquiring about? 8.4 ## 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? 1. Adding the error message to retryableErrors key in the aggregation task ![image](https://global.discourse-cdn.com/sailpoint/original/3X/3/2/32b84ca05aa8eb5e09e76b08dfb3eb1b001c9807.png) 1. Adjusting java settings ![image](https://global.discourse-cdn.com/sailpoint/original/3X/4/b/4b7118921e7ea1f8fa50d7b1c14b66fbedb87231.png)Any help will be appreciated! ---
**Author:** ![vinnysail](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/vinnysail/32/17001_2.png) [@vinnysail](https://developer.sailpoint.com/discuss/u/vinnysail)\ **Post date:** [September 14, 2025, 1:25pm UTC](https://developer.sailpoint.com/discuss/t/ldap-connection-has-been-closed-error-during-account-aggregation/177743/2 "2025-09-14T13:25:43Z")
Hi @shijingg, 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: ` Server is not operational ` 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 ---
**Author:** ![shijingg](https://avatars.discourse-cdn.com/v4/letter/s/e9c0ed/32.png) [@shijingg](https://developer.sailpoint.com/discuss/u/shijingg)\ **Post date:** [September 17, 2025, 2:37am UTC](https://developer.sailpoint.com/discuss/t/ldap-connection-has-been-closed-error-during-account-aggregation/177743/3 "2025-09-17T02:37:12Z")
Hi @vinnysail , just to check for retryableErrors how many times will it retry if it hits the error? ---
**Author:** ![malarvanan12](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/malarvanan12/32/30222_2.png) [@malarvanan12](https://developer.sailpoint.com/discuss/u/malarvanan12)\ **Post date:** [September 17, 2025, 5:57am UTC](https://developer.sailpoint.com/discuss/t/ldap-connection-has-been-closed-error-during-account-aggregation/177743/4 "2025-09-17T05:57:20Z")
> [@shijingg](#): > > 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? > > 1. Adding the error message to retryableErrors key in the aggregation task > > ![image](https://global.discourse-cdn.com/sailpoint/original/3X/3/2/32b84ca05aa8eb5e09e76b08dfb3eb1b001c9807.png) > > 1. Adjusting java settings > > ![image](https://global.discourse-cdn.com/sailpoint/original/3X/4/b/4b7118921e7ea1f8fa50d7b1c14b66fbedb87231.png) > > Any help will be appreciated! Hi, Yes, both approaches you mentioned can help, depending on the root cause: 1. **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. 2. **Adjusting Java settings** : Increasing connection pool size, timeout, or heap can help if the aggregation fails due to resource limits or network latency. ---
**Author:** ![vinnysail](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/vinnysail/32/17001_2.png) [@vinnysail](https://developer.sailpoint.com/discuss/u/vinnysail)\ **Post date:** [September 17, 2025, 1:15pm UTC](https://developer.sailpoint.com/discuss/t/ldap-connection-has-been-closed-error-during-account-aggregation/177743/5 "2025-09-17T13:15:50Z")
Hi @shijingg There is one more parameter maxretries= this should help. Please check and try in your non prod environment before implementing in the live environment. ---
**Author:** ![santhirajumunganda](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/santhirajumunganda/32/38035_2.png) [@santhirajumunganda](https://developer.sailpoint.com/discuss/u/santhirajumunganda)\ **Post date:** [September 18, 2025, 12:15pm UTC](https://developer.sailpoint.com/discuss/t/ldap-connection-has-been-closed-error-during-account-aggregation/177743/6 "2025-09-18T12:15:09Z")
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. Hope this info helps. Raju :expert_ambassador: ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [November 17, 2025, 12:16pm UTC](https://developer.sailpoint.com/discuss/t/ldap-connection-has-been-closed-error-during-account-aggregation/177743/7 "2025-11-17T12:16:01Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.