Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
8.9.0, 8.9.4, 8.10.4, 8.11.3, 8.12.1, 8.13.0
-
6
-
Severity 2 - Major
-
18
-
Description
Issue Summary
Having a small synchronisation interval for user directories may trigger errors on startup, causing directory synchronisation to fail.
Steps to Reproduce
This problem may only happen intermittently:
- Setup an external user directory
- Disable incremental synchronisation
- Set the synchronisation interval to 1 minute
Expected Results
User directory is synchronised
Actual Results
The below exception is thrown in the atlassian-bitbucket.log file:
2023-08-09 09:55:35,754 ERROR [Caesium-1-3] c.a.c.d.DbCachingRemoteDirectory Exception occured when performing full synchronizationio.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.IllegalStateException: Unable to create a tracker when osgi is not running at io.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:156) at io.atlassian.util.concurrent.LazyReference.get(LazyReference.java:116) at io.atlassian.util.concurrent.ResettableLazyReference.get(ResettableLazyReference.java:95) at com.atlassian.stash.internal.crowd.DefaultCrowdDarkFeatureManager.getCrowdDarkFeatureManager(DefaultCrowdDarkFeatureManager.java:58) at com.atlassian.stash.internal.crowd.DefaultCrowdDarkFeatureManager.isEnabled(DefaultCrowdDarkFeatureManager.java:52) at com.atlassian.stash.internal.crowd.DefaultCrowdDarkFeatureManager.isDeleteUserMembershipsBatchingEnabled(DefaultCrowdDarkFeatureManager.java:38) at com.atlassian.crowd.directory.DbCachingRemoteChangeOperations.removeUserMembershipsForGroup(DbCachingRemoteChangeOperations.java:741) ...
Workaround
Set a longer synchronisation interval e.g. 60 minutes (default)
Attachments
Issue Links
- mentioned in
-
Page Loading...