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

Application syncs from Crowd fail due to "com.atlassian.crowd.model.event.AliasEvent" incorrectly invoked

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Low Low
    • 2.6.2
    • None
    • None
    • None

      Problem Summary

      Crowd-integrated applications (e.g. Confluence, JIRA, Stash) can suddenly fail to sync from the Crowd server. This happens seemingly out of the blue without changes to the application.

      Stacktrace shown on the client application side in logs:

      2014-04-29 11:18:38,252 ERROR [scheduler_Worker-5] [atlassian.crowd.directory.DbCachingDirectoryPoller] pollChanges Error occurred while refreshing the cache for directory [ 38076417 ].
com.atlassian.crowd.exception.OperationFailedException: Internal error from Crowd server: class com.atlassian.crowd.model.event.AliasEvent is not supported
	at com.atlassian.crowd.integration.rest.service.RestCrowdClient.handleCommonExceptions(RestCrowdClient.java:1308)
	at com.atlassian.crowd.integration.rest.service.RestCrowdClient.getNewEvents(RestCrowdClient.java:1082)
	at com.atlassian.crowd.directory.RemoteCrowdDirectory.getNewEvents(RemoteCrowdDirectory.java:682)
	at com.atlassian.crowd.directory.ldap.cache.EventTokenChangedCacheRefresher.synchroniseChanges(EventTokenChangedCacheRefresher.java:73)
	at com.atlassian.crowd.directory.DbCachingRemoteDirectory.synchroniseCache(DbCachingRemoteDirectory.java:612)
	at com.atlassian.crowd.manager.directory.DirectorySynchroniserImpl.synchronise(DirectorySynchroniserImpl.java:63)
	at com.atlassian.crowd.directory.DbCachingDirectoryPoller.pollChanges(DbCachingDirectoryPoller.java:50)
	at com.atlassian.crowd.manager.directory.monitor.poller.DirectoryPollerJobBean.executeInternal(DirectoryPollerJobBean.java:29)
	at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:86)
	at org.quartz.core.JobRunShell.run(JobRunShell.java:199)
	at com.atlassian.confluence.schedule.quartz.ConfluenceQuartzThreadPool$1.run(ConfluenceQuartzThreadPool.java:20)
	at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)

      "com.atlassian.crowd.model.event.AliasEvent" should be invoked when a user's alias has been updated/created/removed. However in cases where this has been observed, the integrated application in question does not have aliasing enabled in Crowd. In some cases, there may be an unrelated application (e.g. Google Apps) where aliasing is enabled. Not sure if this is a red herring.

      Workaround

      1. In Crowd, re-set the integrated application's name and password.
      2. In the integrated application's user directory configurations, update the application credentials as appropriate

      This should allow the sync to succeed once more.

              Unassigned Unassigned
              rchang Robert Chang
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: