Synchronizing DVCS accounts on Jira Data Center can result in a NullPointerException

XMLWordPrintable

    • 7.02
    • 23
    • Severity 2 - Major
    • 59

      Issue Summary

      When using Jira Data Center to synchronize DVCS accounts, it's sometimes possible that a NullPointerExcepiton occurs and synchronization for some repositories is interrupted. Synchronization is only picked up again after a certain timeout.

      Note that this does not occur on Jira Server.

      Steps to Reproduce

      1. Set up a DVCS account with Jira Data Center, running at least 2 nodes
      2. Synchronize repositories

      Expected Results

      All repositories become synchronized.

      Actual Results

      Some repositories fail to become synchronized immediately and only become up to date after a certain time.

      The below exception is thrown in the atlassian-jira.log file:

      http-nio-127.0.0.1-8080-exec-1 INFO anonymous 1x101010x1 xxxxxx 127.0.0.1 /rest/bitbucket/1.0/repository/1/sync [rest.external.v1.RepositoryResource] Pull Request Postcommit hook started synchronization for repository [1].
 http-nio-127.0.0.1-8080-exec-1 ERROR anonymous 1x101010x1 xxxxxx 127.0.0.1 /rest/bitbucket/1.0/repository/1/sync [dvcs.sync.impl.DefaultSynchronizer] 
java.lang.NullPointerException
	at com.atlassian.jira.plugins.dvcs.service.GitHubEventContextImpl.savePullRequest(GitHubEventContextImpl.java:47) [jira-dvcs-connector-plugin-5.2.6.jar:?]
	at com.atlassian.jira.plugins.dvcs.spi.github.service.impl.PullRequestReviewCommentPayloadGitHubEventProcessor.process(PullRequestReviewCommentPayloadGitHubEventProcessor.java:46) [jira-dvcs-connector-plugin-5.2.6.jar:?]
	at com.atlassian.jira.plugins.dvcs.spi.github.service.impl.GitHubEventProcessorAggregatorImpl.process(GitHubEventProcessorAggregatorImpl.java:64) [jira-dvcs-connector-plugin-5.2.6.jar:?]
	at com.atlassian.jira.plugins.dvcs.service.GitHubEventServiceImpl$SyncTransactionCallback.doInTransaction(GitHubEventServiceImpl.java:222) [jira-dvcs-connector-plugin-5.2.6.jar:?]
	at com.atlassian.jira.plugins.dvcs.service.GitHubEventServiceImpl$SyncTransactionCallback.doInTransaction(GitHubEventServiceImpl.java:176) [jira-dvcs-connector-plugin-5.2.6.jar:?]
...
	at com.atlassian.jira.plugins.dvcs.service.GitHubEventServiceImpl.synchronize(GitHubEventServiceImpl.java:133) [jira-dvcs-connector-plugin-5.2.6.jar:?]
	at com.atlassian.jira.plugins.dvcs.spi.github.GithubCommunicator.startSynchronisation(GithubCommunicator.java:626) [jira-dvcs-connector-plugin-5.2.6.jar:?]
	at com.atlassian.jira.plugins.dvcs.service.remote.CachingCommunicator.startSynchronisation(CachingCommunicator.java:98) [jira-dvcs-connector-plugin-5.2.6.jar:?]
	at com.atlassian.jira.plugins.dvcs.sync.impl.DefaultSynchronizer.doSync(DefaultSynchronizer.java:173) [jira-dvcs-connector-plugin-5.2.6.jar:?]
	at com.atlassian.jira.plugins.dvcs.service.RepositorySyncServiceImpl.doSync(RepositorySyncServiceImpl.java:440) [jira-dvcs-connector-plugin-5.2.6.jar:?]
	at com.atlassian.jira.plugins.dvcs.service.RepositorySyncServiceImpl.sync(RepositorySyncServiceImpl.java:216) [jira-dvcs-connector-plugin-5.2.6.jar:?]
	at com.atlassian.jira.plugins.dvcs.rest.external.v1.RepositoryResource.startRepositoryPRSync(RepositoryResource.java:339) [jira-dvcs-connector-plugin-5.2.6.jar:?]

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Artur Luszcz (Inactive)
            Reporter:
            Wolfgang Kritzinger
            Votes:
            17 Vote for this issue
            Watchers:
            28 Start watching this issue

              Created:
              Updated:
              Resolved: