com.atlassian.crowd.exception.OperationFailedException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • h3. Description In this bug, a read timeout exception is thrown before the timeout has passed, as can be seen in the logs below: {noformat} 2014-01-29 07:36:47,601 QuartzScheduler_Worker-2 INFO ServiceRunner [atlassian.crowd.directory.DbCachingRemoteDirectory] synchronisation for directory [ 10000 ] starting 2014-01-29 07:36:57,975 QuartzScheduler_Worker-2 INFO ServiceRunner [atlassian.crowd.directory.DbCachingRemoteDirectory] failed synchronisation complete for directory [ 10000 ] in [ 10374ms ] 2014-01-29 07:36:58,084 QuartzScheduler_Worker-2 ERROR ServiceRunner [atlassian.crowd.directory.DbCachingDirectoryPoller] Error occurred while refreshing the cache for directory [ 10000 ]. com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.CommunicationException: avengers-the-initiative.net:389; nested exception is javax.naming.CommunicationException: avengers-the-initiative.net:389 [Root exception is java.net.SocketTimeoutException: connect timed out] at com.atlassian.crowd.directory.SpringLDAPConnector.pageSearchResults(SpringLDAPConnector.java:400) at com.atlassian.crowd.directory.SpringLDAPConnector.searchEntitiesWithRequestControls(SpringLDAPConnector.java:435) at com.atlassian.crowd.directory.MicrosoftActiveDirectory.findTombstonesSince(MicrosoftActiveDirectory.java:882) at com.atlassian.crowd.directory.MicrosoftActiveDirectory.findUserTombstonesSince(MicrosoftActiveDirectory.java:824) {noformat} h3. Expected Behaviour The LDAP connection does not timeout before the *Read Timeout (seconds)* is reached in the User Directory Configuration, for example [Connecting to an LDAP Directory|https://confluence.atlassian.com/display/JIRA/Connecting+to+an+LDAP+Directory#ConnectingtoanLDAPDirectory-ServerSettings]. h3. Actual Behaviour The connection times out before the *Read Timeout (seconds)* interval is met. h3. Verification Review when the synchronisation started in the logs, for example in the below snippet it's {{07:36:47,601}}: {noformat} 2014-01-29 07:36:47,601 QuartzScheduler_Worker-2 INFO ServiceRunner [atlassian.crowd.directory.DbCachingRemoteDirectory] synchronisation for directory [ 10000 ] starting {noformat} And compare that to when the timeout occurs: {noformat} 2014-01-29 07:36:58,084 QuartzScheduler_Worker-2 ERROR ServiceRunner [atlassian.crowd.directory.DbCachingDirectoryPoller] Error occurred while refreshing the cache for directory [ 10000 ]. com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.CommunicationException: avengers-the-initiative.net:389; nested exception is javax.naming.CommunicationException: avengers-the-initiative.net:389 [Root exception is java.net.SocketTimeoutException: connect timed out] {noformat} Here we can see the timeout occurred at {{07:36:58,084}} which is around 11 seconds, and the *Read Timeout (seconds)* was set to 60. It's highly likely this is a result of the Java bug. If the timeout occurs after the interval, this is normal and expected behaviour. For example if the timeout occurred at {{07:37:47,684}} this would be expected behaviour. h3. Cause This bug is triggered randomly in some environments, when the Read Timeout field in LDAP directory properties has been set to non-zero value. This bug is caused by a known [bug (#6968459)|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6968459] affecting Java SE. h3. Workaround Normally these exceptions can be safely ignored as the synchronisation is self-correcting. That is, problems encountered in one synchronisation round will get fixed in the following synchronisation round. If the synchronisation fails to complete successfully repeatedly, a known workaround is to disable read timeout by setting the Read Timeout field in LDAP directory properties to 0. A side-effect of this change is that Crowd will not be able to recover automatically from LDAP requests that take too long to run, which might cause Crowd to stop communicating with LDAP directories until it is restarted. h4. For JIRA 6.3.x customers If you have confirmed that you are experiencing the aforementioned Java bug, we have developed a temporary fix until Oracle fixes the issue in the JDK itself. This is in the form of 2 JARs, a [new version of Crowd for JIRA|https://maven.atlassian.com/service/local/repositories/atlassian-public/content/com/atlassian/crowd/crowd-ldap/2.8.0-OD-6-JIRA-06/crowd-ldap-2.8.0-OD-6-JIRA-06.jar] and a [patched+shaded version of the JDK's LDAP JNDI provider|https://maven.atlassian.com/3rdparty/shaded/atlassian/com/sun/jndi/ldap/atlassian-ldap-jndi-provider/1.8.1-atlassian/atlassian-ldap-jndi-provider-1.8.1-atlassian.jar]. Source for the patched+shaded version of the JDK's LDAP JNDI provider is available at https://bitbucket.org/atlassian/atlassian-ldap-jndi-provider To install these files and apply them as a workaround: - Stop yourJIRA instance - Navigate to JIRA's {{webapp/WEB-INF/lib}} directory. - Replace the existing `crowd-ldap-???.jar` with [crowd-ldap-2.8.0-OD-6-JIRA-06.jar|https://maven.atlassian.com/service/local/repositories/atlassian-public/content/com/atlassian/crowd/crowd-ldap/2.8.0-OD-6-JIRA-06/crowd-ldap-2.8.0-OD-6-JIRA-06.jar] - Add the [atlassian-ldap-jndi-provider-1.8.1-atlassian.jar|https://maven.atlassian.com/3rdparty/shaded/atlassian/com/sun/jndi/ldap/atlassian-ldap-jndi-provider/1.8.1-atlassian/atlassian-ldap-jndi-provider-1.8.1-atlassian.jar] file to this directory as well. - Start your JIRA instance. *IMPORTANT*: This will only work if the you are running Java 8 and a version of JIRA that uses crowd-ldap-2.8.0-OD-6 or compatible (JIRA 6.3.x)
    via by Mark Lassau [Atlassian],
  • h3. Description In this bug, a read timeout exception is thrown before the timeout has passed, as can be seen in the logs below: {noformat} 2014-01-29 07:36:47,601 QuartzScheduler_Worker-2 INFO ServiceRunner [atlassian.crowd.directory.DbCachingRemoteDirectory] synchronisation for directory [ 10000 ] starting 2014-01-29 07:36:57,975 QuartzScheduler_Worker-2 INFO ServiceRunner [atlassian.crowd.directory.DbCachingRemoteDirectory] failed synchronisation complete for directory [ 10000 ] in [ 10374ms ] 2014-01-29 07:36:58,084 QuartzScheduler_Worker-2 ERROR ServiceRunner [atlassian.crowd.directory.DbCachingDirectoryPoller] Error occurred while refreshing the cache for directory [ 10000 ]. com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.CommunicationException: avengers-the-initiative.net:389; nested exception is javax.naming.CommunicationException: avengers-the-initiative.net:389 [Root exception is java.net.SocketTimeoutException: connect timed out] at com.atlassian.crowd.directory.SpringLDAPConnector.pageSearchResults(SpringLDAPConnector.java:400) at com.atlassian.crowd.directory.SpringLDAPConnector.searchEntitiesWithRequestControls(SpringLDAPConnector.java:435) at com.atlassian.crowd.directory.MicrosoftActiveDirectory.findTombstonesSince(MicrosoftActiveDirectory.java:882) at com.atlassian.crowd.directory.MicrosoftActiveDirectory.findUserTombstonesSince(MicrosoftActiveDirectory.java:824) {noformat} h3. Expected Behaviour The LDAP connection does not timeout before the *Read Timeout (seconds)* is reached in the User Directory Configuration, for example [Connecting to an LDAP Directory|https://confluence.atlassian.com/display/JIRA/Connecting+to+an+LDAP+Directory#ConnectingtoanLDAPDirectory-ServerSettings]. h3. Actual Behaviour The connection times out before the *Read Timeout (seconds)* interval is met. h3. Verification Review when the synchronisation started in the logs, for example in the below snippet it's {{07:36:47,601}}: {noformat} 2014-01-29 07:36:47,601 QuartzScheduler_Worker-2 INFO ServiceRunner [atlassian.crowd.directory.DbCachingRemoteDirectory] synchronisation for directory [ 10000 ] starting {noformat} And compare that to when the timeout occurs: {noformat} 2014-01-29 07:36:58,084 QuartzScheduler_Worker-2 ERROR ServiceRunner [atlassian.crowd.directory.DbCachingDirectoryPoller] Error occurred while refreshing the cache for directory [ 10000 ]. com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.CommunicationException: avengers-the-initiative.net:389; nested exception is javax.naming.CommunicationException: avengers-the-initiative.net:389 [Root exception is java.net.SocketTimeoutException: connect timed out] {noformat} Here we can see the timeout occurred at {{07:36:58,084}} which is around 11 seconds, and the *Read Timeout (seconds)* was set to 60. It's highly likely this is a result of the Java bug. If the timeout occurs after the interval, this is normal and expected behaviour. For example if the timeout occurred at {{07:37:47,684}} this would be expected behaviour. h3. Cause This bug is triggered randomly in some environments, when the Read Timeout field in LDAP directory properties has been set to non-zero value. This bug is caused by a known [bug (#6968459)|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6968459] affecting Java SE. h3. Workaround Normally these exceptions can be safely ignored as the synchronisation is self-correcting. That is, problems encountered in one synchronisation round will get fixed in the following synchronisation round. If the synchronisation fails to complete successfully repeatedly, a known workaround is to disable read timeout by setting the Read Timeout field in LDAP directory properties to 0. A side-effect of this change is that Crowd will not be able to recover automatically from LDAP requests that take too long to run, which might cause Crowd to stop communicating with LDAP directories until it is restarted. h4. For JIRA 6.3.x customers If you have confirmed that you are experiencing the aforementioned Java bug, we have developed a temporary fix until Oracle fixes the issue in the JDK itself. This is in the form of 2 JARs, a [new version of Crowd for JIRA|https://maven.atlassian.com/service/local/repositories/atlassian-public/content/com/atlassian/crowd/crowd-ldap/2.8.0-OD-6-JIRA-06/crowd-ldap-2.8.0-OD-6-JIRA-06.jar] and a [patched+shaded version of the JDK's LDAP JNDI provider|https://maven.atlassian.com/3rdparty/shaded/atlassian/com/sun/jndi/ldap/atlassian-ldap-jndi-provider/1.8.1-atlassian/atlassian-ldap-jndi-provider-1.8.1-atlassian.jar]. Source for the patched+shaded version of the JDK's LDAP JNDI provider is available at https://bitbucket.org/atlassian/atlassian-ldap-jndi-provider To install these files and apply them as a workaround: - Stop yourJIRA instance - Navigate to JIRA's {{webapp/WEB-INF/lib}} directory. - Replace the existing `crowd-ldap-???.jar` with [crowd-ldap-2.8.0-OD-6-JIRA-06.jar|https://maven.atlassian.com/service/local/repositories/atlassian-public/content/com/atlassian/crowd/crowd-ldap/2.8.0-OD-6-JIRA-06/crowd-ldap-2.8.0-OD-6-JIRA-06.jar] - Add the [atlassian-ldap-jndi-provider-1.8.1-atlassian.jar|https://maven.atlassian.com/3rdparty/shaded/atlassian/com/sun/jndi/ldap/atlassian-ldap-jndi-provider/1.8.1-atlassian/atlassian-ldap-jndi-provider-1.8.1-atlassian.jar] file to this directory as well. - Start your JIRA instance. *IMPORTANT*: This will only work if the you are running Java 8 and a version of JIRA that uses crowd-ldap-2.8.0-OD-6 or compatible (JIRA 6.3.x)
    via by Mark Lassau [Atlassian],
  • h1. Symptoms An org.springframework.ldap.UncategorizedLdapException exception is thrown when testing searching users/groups while setting up a new ActiveDirectory connector. The exception is uncaught, therefore the user is shown a blank screen, and an stacktrace appears in the logs. h1. Steps to reproduce # Click on 'Add directory' # Select 'Connector' # Enter a name # Switch to the 2nd tab ('Connector') # Pick 'Microsoft Active Directory' # Enter a correct URL (e.g. ldap://crowd-ad1:389/), a correct base DN and correct credentials # Optionally, click on 'Test connection'. The test should pass. # Change to the 3rd tab ('Configuration'). # Click on 'Test search'. Expected result: an error message is displayed on the screen to inform the user. Actual result: blank screen, and stacktrace in the logs. h1. Stacktrace {code} 2013-01-29 17:10:31,412 http-8095-6 FATAL [springframework.ldap.control.AbstractRequestControlDirContextProcessor] No matching response control found for paged results - looking for 'class javax.naming.ldap.PagedResultsResponseControl 2013-01-29 17:10:31,412 http-8095-6 ERROR [console.action.directory.CreateDirectory] org.springframework.ldap.UncategorizedLdapException: Uncategorized exception occured during LDAP processing; nested exception is javax.naming.NamingException: [LDAP: error code 1 - 00000000: LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece]; remaining name 'dc=sydney,dc=atlassian,dc=com' com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.UncategorizedLdapException: Uncategorized exception occured during LDAP processing; nested exception is javax.naming.NamingException: [LDAP: error code 1 - 00000000: LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece]; remaining name 'dc=sydney,dc=atlassian,dc=com' at com.atlassian.crowd.directory.SpringLDAPConnector.pageSearchResults(SpringLDAPConnector.java:385) at com.atlassian.crowd.directory.SpringLDAPConnector.searchEntitiesWithRequestControls(SpringLDAPConnector.java:418) at com.atlassian.crowd.directory.SpringLDAPConnector.searchEntities(SpringLDAPConnector.java:403) at com.atlassian.crowd.directory.SpringLDAPConnector.searchUserObjects(SpringLDAPConnector.java:592) at com.atlassian.crowd.directory.SpringLDAPConnector.searchUsers(SpringLDAPConnector.java:958) at com.atlassian.crowd.console.action.directory.LDAPConfigurationTester$Strategy$1.search(LDAPConfigurationTester.java:29) at com.atlassian.crowd.console.action.directory.LDAPConfigurationTesterImpl.canFindLdapObjects(LDAPConfigurationTesterImpl.java:27) at com.atlassian.crowd.console.action.directory.CreateConnector.doTestSearch(CreateConnector.java:238) at com.atlassian.crowd.console.action.directory.CreateConnector.doTestPrincipalSearch(CreateConnector.java:220) ... Caused by: org.springframework.ldap.UncategorizedLdapException: Uncategorized exception occured during LDAP processing; nested exception is javax.naming.NamingException: [LDAP: error code 1 - 00000000: LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece]; remaining name 'dc=sydney,dc=atlassian,dc=com' at org.springframework.ldap.support.LdapUtils.convertLdapException(LdapUtils.java:217) at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:319) at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:237) at com.atlassian.crowd.directory.ldap.LdapTemplateWithClassLoaderWrapper$4.call(LdapTemplateWithClassLoaderWrapper.java:92) at com.atlassian.crowd.directory.ldap.LdapTemplateWithClassLoaderWrapper$4.call(LdapTemplateWithClassLoaderWrapper.java:89) at com.atlassian.crowd.directory.ldap.LdapTemplateWithClassLoaderWrapper.invokeWithContextClassLoader(LdapTemplateWithClassLoaderWrapper.java:47) at com.atlassian.crowd.directory.ldap.LdapTemplateWithClassLoaderWrapper.search(LdapTemplateWithClassLoaderWrapper.java:89) at com.atlassian.crowd.directory.SpringLDAPConnector.pageSearchResults(SpringLDAPConnector.java:352) ... 134 more Caused by: javax.naming.NamingException: [LDAP: error code 1 - 00000000: LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece]; remaining name 'dc=sydney,dc=atlassian,dc=com' at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3127) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3033) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2840) at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1849) at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1772) at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:386) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:356) at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:276) at sun.reflect.GeneratedMethodAccessor342.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.springframework.ldap.transaction.compensating.manager.TransactionAwareDirContextInvocationHandler.invoke(TransactionAwareDirContextInvocationHandler.java:92) at $Proxy146.search(Unknown Source) at org.springframework.ldap.core.LdapTemplate$3.executeSearch(LdapTemplate.java:231) at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:293) {code}
    via by Diego Berrueta Munoz,
  • h1. Symptoms An org.springframework.ldap.UncategorizedLdapException exception is thrown when testing searching users/groups while setting up a new ActiveDirectory connector. The exception is uncaught, therefore the user is shown a blank screen, and an stacktrace appears in the logs. h1. Steps to reproduce # Click on 'Add directory' # Select 'Connector' # Enter a name # Switch to the 2nd tab ('Connector') # Pick 'Microsoft Active Directory' # Enter a correct URL (e.g. ldap://crowd-ad1:389/), a correct base DN and correct credentials # Optionally, click on 'Test connection'. The test should pass. # Change to the 3rd tab ('Configuration'). # Click on 'Test search'. Expected result: an error message is displayed on the screen to inform the user. Actual result: blank screen, and stacktrace in the logs. h1. Stacktrace {code} 2013-01-29 17:10:31,412 http-8095-6 FATAL [springframework.ldap.control.AbstractRequestControlDirContextProcessor] No matching response control found for paged results - looking for 'class javax.naming.ldap.PagedResultsResponseControl 2013-01-29 17:10:31,412 http-8095-6 ERROR [console.action.directory.CreateDirectory] org.springframework.ldap.UncategorizedLdapException: Uncategorized exception occured during LDAP processing; nested exception is javax.naming.NamingException: [LDAP: error code 1 - 00000000: LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece]; remaining name 'dc=sydney,dc=atlassian,dc=com' com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.UncategorizedLdapException: Uncategorized exception occured during LDAP processing; nested exception is javax.naming.NamingException: [LDAP: error code 1 - 00000000: LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece]; remaining name 'dc=sydney,dc=atlassian,dc=com' at com.atlassian.crowd.directory.SpringLDAPConnector.pageSearchResults(SpringLDAPConnector.java:385) at com.atlassian.crowd.directory.SpringLDAPConnector.searchEntitiesWithRequestControls(SpringLDAPConnector.java:418) at com.atlassian.crowd.directory.SpringLDAPConnector.searchEntities(SpringLDAPConnector.java:403) at com.atlassian.crowd.directory.SpringLDAPConnector.searchUserObjects(SpringLDAPConnector.java:592) at com.atlassian.crowd.directory.SpringLDAPConnector.searchUsers(SpringLDAPConnector.java:958) at com.atlassian.crowd.console.action.directory.LDAPConfigurationTester$Strategy$1.search(LDAPConfigurationTester.java:29) at com.atlassian.crowd.console.action.directory.LDAPConfigurationTesterImpl.canFindLdapObjects(LDAPConfigurationTesterImpl.java:27) at com.atlassian.crowd.console.action.directory.CreateConnector.doTestSearch(CreateConnector.java:238) at com.atlassian.crowd.console.action.directory.CreateConnector.doTestPrincipalSearch(CreateConnector.java:220) ... Caused by: org.springframework.ldap.UncategorizedLdapException: Uncategorized exception occured during LDAP processing; nested exception is javax.naming.NamingException: [LDAP: error code 1 - 00000000: LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece]; remaining name 'dc=sydney,dc=atlassian,dc=com' at org.springframework.ldap.support.LdapUtils.convertLdapException(LdapUtils.java:217) at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:319) at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:237) at com.atlassian.crowd.directory.ldap.LdapTemplateWithClassLoaderWrapper$4.call(LdapTemplateWithClassLoaderWrapper.java:92) at com.atlassian.crowd.directory.ldap.LdapTemplateWithClassLoaderWrapper$4.call(LdapTemplateWithClassLoaderWrapper.java:89) at com.atlassian.crowd.directory.ldap.LdapTemplateWithClassLoaderWrapper.invokeWithContextClassLoader(LdapTemplateWithClassLoaderWrapper.java:47) at com.atlassian.crowd.directory.ldap.LdapTemplateWithClassLoaderWrapper.search(LdapTemplateWithClassLoaderWrapper.java:89) at com.atlassian.crowd.directory.SpringLDAPConnector.pageSearchResults(SpringLDAPConnector.java:352) ... 134 more Caused by: javax.naming.NamingException: [LDAP: error code 1 - 00000000: LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece]; remaining name 'dc=sydney,dc=atlassian,dc=com' at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3127) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3033) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2840) at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1849) at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1772) at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:386) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:356) at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:276) at sun.reflect.GeneratedMethodAccessor342.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.springframework.ldap.transaction.compensating.manager.TransactionAwareDirContextInvocationHandler.invoke(TransactionAwareDirContextInvocationHandler.java:92) at $Proxy146.search(Unknown Source) at org.springframework.ldap.core.LdapTemplate$3.executeSearch(LdapTemplate.java:231) at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:293) {code}
    via by Diego Berrueta,
    • com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.CommunicationException: avengers-the-initiative.net:389; nested exception is javax.naming.CommunicationException: avengers-the-initiative.net:389 [Root exception is java.net.SocketTimeoutException: connect timed out] at com.atlassian.crowd.directory.SpringLDAPConnector.pageSearchResults(SpringLDAPConnector.java:400) at com.atlassian.crowd.directory.SpringLDAPConnector.searchEntitiesWithRequestControls(SpringLDAPConnector.java:435) at com.atlassian.crowd.directory.MicrosoftActiveDirectory.findTombstonesSince(MicrosoftActiveDirectory.java:882) at com.atlassian.crowd.directory.MicrosoftActiveDirectory.findUserTombstonesSince(MicrosoftActiveDirectory.java:824)
    No Bugmate found.