My crowd application is unable to sync with AD however it sync's well with JIRA. Below is the error message that i get in log files.
I tried increasing the connection timeout setting to 20secs which was earlier 10secs. Could you please advice? Note- crowd version 2.4.0
Below is the error log-
2015-07-29 02:02:57,166 scheduler_Worker-7 INFO [atlassian.crowd.directory.DbCachingRemoteDirectory] failed synchronisation complete in [ 24026ms ]
2015-07-29 02:02:57,188 scheduler_Worker-7 ERROR [atlassian.crowd.directory.DbCachingDirectoryPoller] Error occurred while refreshing the cache for directory [ 32771 ].
com.atlassian.crowd.exception.OperationFailedException: java.util.concurrent.ExecutionException: com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.PartialResultException: nested exception is javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: zs.local:389 [Root exception is java.net.SocketTimeoutException: connect timed out]]
I've found the following message:
zs.local:389 [Root exception is java.net.SocketTimeoutException: connect timed out]]
This means Crowd cannot communicate to zs.local or if you have multiple domains, they aren't replicating properly. Please check if this host is correct and your AD's are replicating.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs