Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-4496

Add logging explaining why incremental sync fails

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      Currently

      When an incremental sync fails, the logs are not very helpful in determining the cause. This makes it tough for support and DoS to diagnose these kinds of Crowd issues (which pop up way too much).

      2015-09-14 17:16:31,320 INFO [scheduler_Worker-7] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache INCREMENTAL synchronisation for directory [ 786433 ] starting
2015-09-14 17:16:31,321 INFO [scheduler_Worker-7] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache Attempting INCREMENTAL synchronisation for directory [ 786433 ]
2015-09-14 17:16:31,358 INFO [scheduler_Worker-7] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache Incremental synchronisation for directory [ 786433 ] was not completed, falling back to a full synchronisation
2015-09-14 17:16:31,358 INFO [scheduler_Worker-7] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache INCREMENTAL synchronisation for directory [ 786433 ] was not successful, attempting FULL

      Solution

      Something like this would be more ideal:

      2015-09-14 17:16:31,320 INFO [scheduler_Worker-7] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache INCREMENTAL synchronisation for directory [ 786433 ] starting
2015-09-14 17:16:31,321 INFO [scheduler_Worker-7] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache Attempting INCREMENTAL synchronisation for directory [ 786433 ]
2015-09-14 17:16:31,352 ERROR [scheduler_Worker-7] [directory.ldap.cache.EventTokenChangedCacheRefresher] synchroniseChanges Incremental synchronisation failed: com.atlassian.crowd.event.user.UserRenamedEvent is not supported by incremental sync.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. CONFSERVER-33455 After renaming a user in Active Directory, Confluence syncs that user in as a new user (if and only if Confluence is connected to JIRA or Crowd, which is in turn connected to LDAP)

          • Medium - Medium priority issues
          • Closed
          mentioned in

          Page Loading...

          Activity

            People

              briosa Blake Riosa (Inactive)
              briosa Blake Riosa (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: