Hi,
I found many this message in my JIRA server log.
2014-04-30 22:21:31,687 QuartzScheduler_Worker-0 INFO ServiceRunner [atlassian.crowd.directory.DbCachingRemoteDirectory] synchronisation for directory [ 10000 ] starting
2014-04-30 22:21:31,711 QuartzScheduler_Worker-0 WARN ServiceRunner [directory.ldap.cache.EventTokenChangedCacheRefresher] Incremental synchronisation is not available. Falling back to full synchronisation
com.atlassian.crowd.event.IncrementalSynchronisationNotAvailableException
at com.atlassian.crowd.integration.rest.service.RestCrowdClient.getCurrentEventToken(RestCrowdClient.java:1055)
at com.atlassian.crowd.directory.RemoteCrowdDirectory.getCurrentEventToken(RemoteCrowdDirectory.java:658)
at com.atlassian.crowd.directory.ldap.cache.EventTokenChangedCacheRefresher.synchroniseAll(EventTokenChangedCacheRefresher.java:54)
at com.atlassian.crowd.directory.DbCachingRemoteDirectory.synchroniseCache(DbCachingRemoteDirectory.java:855)
at com.atlassian.crowd.manager.directory.DirectorySynchroniserImpl.synchronise(DirectorySynchroniserImpl.java:75)
at com.atlassian.crowd.directory.DbCachingDirectoryPoller.pollChanges(DbCachingDirectoryPoller.java:50)
at com.atlassian.crowd.manager.directory.monitor.poller.DirectoryPollerJob.execute(DirectoryPollerJob.java:34)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
2014-04-30 22:21:31,834 QuartzScheduler_Worker-0 INFO ServiceRunner [directory.ldap.cache.RemoteDirectoryCacheRefresher] found [ 952 ] remote users in [ 123ms ]
Could you explain why this message are occurred very often in my server?
Thanks
There can be different reasons why the incremental synchronization might not be available. For example, if you have opted not to cache the difrectory while configuring it in Crowd, it will do only full synchronization.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.