DVCS Bitbucket Repository Synchronization Fails

XMLWordPrintable

    • 18
    • Severity 2 - Major

      NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.

      Summary

      Bitbucket repositories periodically fail to synchronize. The error message on the DVCS accounts page indicates the failure and advises checking the application logs which are not exposed in Cloud.

      Environment

      Cloud

      Steps to Reproduce

      1. Configure DVCS account in JIRA Cloud
      2. Synchronize repositories as scheduled or manually

      Expected Results

      Repositories synchronize successfully

      Actual Results

      The below exception is thrown in the JIRA application log and repository synchronization fails:

      @40000000568feee92d4e424c 2016-01-08 11:16:15,759 DVCSConnector.MessageExecutor:thread-1 ERROR anonymous 144x957x1 -  /rest/bitbucket/1.
0/repository/21/sync [c.a.j.p.d.service.message.MessageConsumer] Synchronization failed: null
@40000000568feee92d4e4634 com.atlassian.jira.plugins.dvcs.spi.bitbucket.clientlibrary.request.BitbucketRequestException$BadRequest_400
@40000000568feee92d4e7ce4 	at com.atlassian.jira.plugins.dvcs.spi.bitbucket.clientlibrary.request.BaseRemoteRequestor.checkAndCreateRemoteResponse(BaseRemoteRequestor.jav
a:284)
@40000000568feee92d4e9454 	at com.atlassian.jira.plugins.dvcs.spi.bitbucket.clientlibrary.request.BaseRemoteRequestor.request(BaseRemoteRequestor.java:230)
@40000000568feee92d4e9c24 	at com.atlassian.jira.plugins.dvcs.spi.bitbucket.clientlibrary.request.BaseRemoteRequestor.requestWithoutPayload(BaseRemoteRequestor.java:206)
@40000000568feee92d4ea00c 	at com.atlassian.jira.plugins.dvcs.spi.bitbucket.clientlibrary.request.BaseRemoteRequestor.lambda$getWithRetry$15(BaseRemoteRequestor.java:116)
@40000000568feee92d4eafac 	at com.atlassian.jira.plugins.dvcs.spi.bitbucket.clientlibrary.request.BaseRemoteRequestor$$Lambda$724/15533640.call(Unknown Source)
@40000000568feee92d4ecb04 	at com.atlassian.jira.plugins.dvcs.spi.bitbucket.clientlibrary.client.BadRequestRetryer.retry(BadRequestRetryer.java:61)
@40000000568feee92d4eceec 	at com.atlassian.jira.plugins.dvcs.spi.bitbucket.clientlibrary.client.BadRequestRetryer.retry(BadRequestRetryer.java:22)
@40000000568feee92d4eceec 	at com.atlassian.jira.plugins.dvcs.spi.bitbucket.clientlibrary.request.BaseRemoteRequestor.getWithRetry(BaseRemoteRequestor.java:116)
@40000000568feee92d4ede8c 	at com.atlassian.jira.plugins.dvcs.spi.bitbucket.clientlibrary.request.BaseRemoteRequestor.get(BaseRemoteRequestor.java:62)
@40000000568feee92d4ee274 	at com.atlassian.jira.plugins.dvcs.spi.bitbucket.clientlibrary.restpoints.PullRequestRemoteRestpoint.getCount(PullRequestRemoteRestpoint.java:1
34)
@40000000568feee92d4ee65c 	at com.atlassian.jira.plugins.dvcs.sync.BitbucketSynchronizeActivityMessageConsumer.lambda$ensurePullRequestPresent$3(BitbucketSynchronizeActiv
ityMessageConsumer.java:236)
@40000000568feee92d4ef5fc 	at com.atlassian.jira.plugins.dvcs.sync.BitbucketSynchronizeActivityMessageConsumer$$Lambda$929/1704709.call(Unknown Source)
@40000000568feee92d4ef9e4 	at com.atlassian.jira.plugins.dvcs.sync.FlightTimeInterceptor.execute(FlightTimeInterceptor.java:25)
@40000000568feee92d4f1154 	at com.atlassian.jira.plugins.dvcs.sync.BitbucketSynchronizeActivityMessageConsumer.ensurePullRequestPresent(BitbucketSynchronizeActivityMessag
eConsumer.java:236)
@40000000568feee92d4f153c 	at com.atlassian.jira.plugins.dvcs.sync.BitbucketSynchronizeActivityMessageConsumer.processActivity(BitbucketSynchronizeActivityMessageConsumer
.java:199)
@40000000568feee92d4f1924 	at com.atlassian.jira.plugins.dvcs.sync.BitbucketSynchronizeActivityMessageConsumer.onReceive(BitbucketSynchronizeActivityMessageConsumer.java:
139)
@40000000568feee92d4f4804 	at com.atlassian.jira.plugins.dvcs.sync.BitbucketSynchronizeActivityMessageConsumer.onReceive(BitbucketSynchronizeActivityMessageConsumer.java:
69)
@40000000568feee92d4f4bec 	at com.atlassian.jira.plugins.dvcs.service.MessageExecutor$MessageRunnable.doRun(MessageExecutor.java:369)
@40000000568feee92d4f4bec 	at com.atlassian.jira.plugins.dvcs.service.MessageExecutor$ReleaseTokenAndEnqueueNextMessage.run(MessageExecutor.java:277)
@40000000568feee92d4f5b8c 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
@40000000568feee92d4f5b8c 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
@40000000568feee92d4f72fc 	at java.lang.Thread.run(Thread.java:745)
@40000000568feeea1a79dadc 2016-01-08 11:16:16,444 DVCSConnector.MessageExecutor:thread-1 WARN anonymous 144x957x1 -  /rest/bitbucket/1.0
/repository/21/sync [c.a.j.p.d.s.b.clientlibrary.request.BaseRemoteRequestor] Failed to properly execute request [GET https://bitbucket.org/!api/2.0/repositories/.... 
@40000000568feeea1a79e694     Params: org.apache.http.params.BasicHttpParams@1e9ad68, 
@40000000568feeea1a79e694     Response code 400

      Workaround

      Resetting the OAuth settings or removing and re-adding the account has alleviated the synchronization errors in some but not all cases. No official workaround at present.

            Assignee:
            Ahmed Fouad (Inactive)
            Reporter:
            Russ Gould [Atlassian] (Inactive)
            Votes:
            4 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: