Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-14273

GitHub pull request sync failed with message: "Multiple GitHubEvents exists with the same id"

XMLWordPrintable

      Somehow there are duplicated entries in the GITHUB_EVENT_ID table.

      @4000000053a09940285a391c 2014-06-17 12:38:30,676 TP-Processor7 INFO anonymous 758x100659x1 - 192.30.252.33,165.254.226.65 /rest/bitbucket/1.0/repository/25/sync [plugins.dvcs.rest.RootResource] Pull Request Postcommit hook started synchronization for repository [25].
@4000000053a099420c95d31c 2014-06-17 12:38:32,207 TP-Processor7 ERROR anonymous 758x100659x1 - 192.30.252.33,165.254.226.65 /rest/bitbucket/1.0/repository/25/sync [dvcs.sync.impl.DefaultSynchronizer] Multiple GitHubEvents exists with the same id: 2132303445
@4000000053a099420c95ded4 java.lang.RuntimeException: Multiple GitHubEvents exists with the same id: 2132303445
@4000000053a099420c95e2bc       at com.atlassian.jira.plugins.dvcs.dao.impl.GitHubEventDAOImpl.getByGitHubId(GitHubEventDAOImpl.java:97)
@4000000053a099420c95e6a4       at com.atlassian.jira.plugins.dvcs.service.GitHubEventServiceImpl$1.doInTransaction(GitHubEventServiceImpl.java:109)
@4000000053a099420c963c94       at com.atlassian.jira.plugins.dvcs.service.GitHubEventServiceImpl$1.doInTransaction(GitHubEventServiceImpl.java:97)
@4000000053a099420c96407c       at com.atlassian.sal.core.transaction.HostContextTransactionTemplate$1.doInTransaction(HostContextTransactionTemplate.java:25)
@4000000053a099420c964464       at com.atlassian.jira.DefaultHostContextAccessor.doInTransaction(DefaultHostContextAccessor.java:34)
@4000000053a099420c964c34       at sun.reflect.GeneratedMethodAccessor173.invoke(Unknown Source)
@4000000053a099420c96501c       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
@4000000053a099420c965fbc       at java.lang.reflect.Method.invoke(Method.java:597)
@4000000053a099420c9663a4       at com.atlassian.plugin.osgi.hostcomponents.impl.DefaultComponentRegistrar$ContextClassLoaderSettingInvocationHandler.invoke(DefaultComponentRegistrar.java:129)
@4000000053a099420c96678c       at $Proxy287.doInTransaction(Unknown Source)
@4000000053a099420c96678c       at sun.reflect.GeneratedMethodAccessor173.invoke(Unknown Source)
@4000000053a099420c966f5c       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
@4000000053a099420c967344       at java.lang.reflect.Method.invoke(Method.java:597)
@4000000053a099420c967344       at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:154)
@4000000053a099420c96772c       at $Proxy287.doInTransaction(Unknown Source)
@4000000053a099420c967efc       at com.atlassian.sal.core.transaction.HostContextTransactionTemplate.execute(HostContextTransactionTemplate.java:21)
@4000000053a099420c9682e4       at sun.reflect.GeneratedMethodAccessor215.invoke(Unknown Source)
@4000000053a099420c9682e4       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
@4000000053a099420c9686cc       at java.lang.reflect.Method.invoke(Method.java:597)

      Workaround: do a full synchronization on the repository.

            [JSWSERVER-14273] GitHub pull request sync failed with message: "Multiple GitHubEvents exists with the same id"

            Benjamin Morgan (Inactive) added a comment -

            loic.dewerchin We are working on including this in an upcoming JIRA server release, I will make sure we update the ticket when it is released.

            Benjamin Morgan (Inactive) added a comment - loic.dewerchin We are working on including this in an upcoming JIRA server release, I will make sure we update the ticket when it is released.

            Loïc Dewerchin added a comment -

            Hello,

            we had/have the same problem with three repo's : two @github.com , one at our own Github enterprise
            Tried the workaround , full synchronization, and it worked for the repo @ our own github instance
            Failed @ github.com with the expected exception

            API rate limit exceeded for .... (403)

            Nothing much to do about I guess, so we are hoping for a fix from Atlassian's side ...
            The issue is marked as resolved in version 2.3.3, which seems odd as the latest release not so long ago is 2.1.28
            https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugins.jira-bitbucket-connector-plugin/versions

            Am I missing something here? And when will this fix be available for server instances?

            best regards
            Loïc

            Loïc Dewerchin added a comment - Hello, we had/have the same problem with three repo's : two @github.com , one at our own Github enterprise Tried the workaround , full synchronization, and it worked for the repo @ our own github instance Failed @ github.com with the expected exception API rate limit exceeded for .... (403) Nothing much to do about I guess, so we are hoping for a fix from Atlassian's side ... The issue is marked as resolved in version 2.3.3, which seems odd as the latest release not so long ago is 2.1.28 https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugins.jira-bitbucket-connector-plugin/versions Am I missing something here? And when will this fix be available for server instances? best regards Loïc

            Benjamin Morgan (Inactive) added a comment -

            This has been resolved in the latest release to cloud

            Benjamin Morgan (Inactive) added a comment - This has been resolved in the latest release to cloud

            Graze Atlassian Admin added a comment -

            This has happened to us too. It seems to correlate with doing a force push to GitHub. What is the ETA on a fix?

            Graze Atlassian Admin added a comment - This has happened to us too. It seems to correlate with doing a force push to GitHub. What is the ETA on a fix?

            Roman Serazhiev (Inactive) added a comment -

            Still happening for us as well. Happened twice within couple of months already. DVCS 2.1.23, JIRA 6.3.7

            Roman Serazhiev (Inactive) added a comment - Still happening for us as well. Happened twice within couple of months already. DVCS 2.1.23, JIRA 6.3.7

            shilin yi added a comment - - edited

            The DVCS Connector plugin is completely broken when I try to integrate with github:

            After the setup I could see all my github repositories in the JIRA admin DVCS Accounts page, but the Sync of each repository is failed, in each repository, there is an error message: 
            Sync Failed: Error during sync. See server logs.

            And it could not be fixed by the button of "Sync Repo".

            From the support of atlassian, it is related to this bug. Would you please set priority for this issue and get it fixed?

            Thanks.

            ----------

            Here is the support ticket:

            https://support.atlassian.com/servicedesk/customer/portal/22/JSP-216580

            And my JIRA system info :

            IRA DVCS Connector Plugin - 2.2.9-D20141204T035127
            atlassian-data-center-compatible: true

            Version 6.4-OD-13-024
            Build Number 64009
            Build Date Wed Jan 07 00:00:00 GMT 2015
            Build Revision 4e0827c37e303967594a5f3fc0256fd50d5d5ec0
            Server ID B14E-GL73-6FKZ-OP3B
            Last Upgrade 12/Jan/15 9:25 AM (v6.4-OD-11-012#64007)

            shilin yi added a comment - - edited The DVCS Connector plugin is completely broken when I try to integrate with github: After the setup I could see all my github repositories in the JIRA admin DVCS Accounts page, but the Sync of each repository is failed, in each repository, there is an error message:  Sync Failed: Error during sync. See server logs. And it could not be fixed by the button of "Sync Repo". From the support of atlassian, it is related to this bug. Would you please set priority for this issue and get it fixed? Thanks. ---------- Here is the support ticket: https://support.atlassian.com/servicedesk/customer/portal/22/JSP-216580 And my JIRA system info : IRA DVCS Connector Plugin - 2.2.9-D20141204T035127 atlassian-data-center-compatible: true Version 6.4-OD-13-024 Build Number 64009 Build Date Wed Jan 07 00:00:00 GMT 2015 Build Revision 4e0827c37e303967594a5f3fc0256fd50d5d5ec0 Server ID B14E-GL73-6FKZ-OP3B Last Upgrade 12/Jan/15 9:25 AM (v6.4-OD-11-012#64007)

            Benjamin Morgan (Inactive) added a comment -

            Based on some investigation this is still occurring.

            The issue is occurs because of a timing issue around fetching the latest events from Github. The latest events API will return the most recent 300 events in the repository (commits, pull requests etc.). During synchronisation duplicate events can occasionally arrive, these are normally filtered out but we are investigating why some are still being recorded.

            The work around is to perform a full synchronization, alternatively the issue should also resolve once the duplicate is no longer one of the 300 most recent events.

            Benjamin Morgan (Inactive) added a comment - Based on some investigation this is still occurring. The issue is occurs because of a timing issue around fetching the latest events from Github. The latest events API will return the most recent 300 events in the repository (commits, pull requests etc.). During synchronisation duplicate events can occasionally arrive, these are normally filtered out but we are investigating why some are still being recorded. The work around is to perform a full synchronization, alternatively the issue should also resolve once the duplicate is no longer one of the 300 most recent events.

            Benjamin Morgan (Inactive) added a comment -

            The release on the 20th (JIRA 0D 8) was cancelled, next release is due on 3 November

            Benjamin Morgan (Inactive) added a comment - The release on the 20th (JIRA 0D 8) was cancelled, next release is due on 3 November

            ZehuaA added a comment -

            The fix for this issue is scheduled to be released to OnDemand on 20 Oct 2014.

            ZehuaA added a comment - The fix for this issue is scheduled to be released to OnDemand on 20 Oct 2014.

              bmorgan Benjamin Morgan (Inactive)
              zliu ZehuaA
              Affected customers:
              7 This affects my team
              Watchers:
              28 Start watching this issue

                Created:
                Updated:
                Resolved: