Can you explain why this message occurred in JIRA log?


I found many this message in my JIRA server log.

2014-04-30 22:21:31,687 QuartzScheduler_Worker-0 INFO ServiceRunner [] 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










at org.quartz.simpl.SimpleThreadPool$

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?


1 answer

0 votes

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,531 views 15 21
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you