JIRA DVCS does not re-establish the sync connection if memcache is expiring from Bitbucket Cloud side

XMLWordPrintable

    • 7.09
    • 8
    • Severity 3 - Minor
    • 1

      Summary

      When JIRA DVCS connector is performing a long synchronisation from Bitbucket Cloud, memcache from Bitbucket side is expiring and JIRA DVCS connector does not re-establish the connection and will failed the sync process

      Environment

      • JIRA Software with DVCS connector

      Steps to Reproduce

      1. In JIRA Software, link Bitbucket Cloud under the DVCS account configuration
      2. JIRA will then add the corresponding repository
      3. Under certain circumstances, sometimes JIRA will failed to perform the synchronisation due to network issue or some other factor

      Expected Results

      JIRA DVCS connector should be able aware of the memcache is expiring and try to re-establish a reconnection

      Actual Results

      JIRA DVCS connector is not aware of the memcache expiring and failed to re-establish a reconnection and following error occurred:

      2018-08-31 11:20:38,363 DVCSConnector.MessageExecutor:thread-15 ERROR ServiceRunner     [c.a.j.p.d.service.message.MessageConsumer] Synchronization failed: {"type": "error", "error": {"message": "Traversal state lost. Unable to resume."}} (Sentry: N/A)
com.atlassian.jira.plugins.dvcs.spi.bitbucket.clientlibrary.request.BitbucketRequestException$InternalServerError_500: {"type": "error", "error": {"message": "Traversal state lost. Unable to resume."}} (Sentry: N/A)
	at com.atlassian.jira.plugins.dvcs.spi.bitbucket.clientlibrary.request.BaseRemoteRequestor.checkAndCreateRemoteResponse(BaseRemoteRequestor.java:270)
	at com.atlassian.jira.plugins.dvcs.spi.bitbucket.clientlibrary.request.BaseRemoteRequestor.request(BaseRemoteRequestor.java:226)
	at com.atlassian.jira.plugins.dvcs.spi.bitbucket.clientlibrary.request.BaseRemoteRequestor.requestWithoutPayload(BaseRemoteRequestor.java:210)
	at com.atlassian.jira.plugins.dvcs.spi.bitbucket.clientlibrary.request.BaseRemoteRequestor.lambda$getWithRetry$0(BaseRemoteRequestor.java:131)
	at com.atlassian.jira.plugins.dvcs.spi.bitbucket.clientlibrary.client.BadRequestRetryer.retry(BadRequestRetryer.java:27)
	at com.atlassian.jira.plugins.dvcs.spi.bitbucket.clientlibrary.client.BadRequestRetryer.retry(BadRequestRetryer.java:20)

      Notes

      This behaviour is only reproducible when JIRA failed to perform the sync from the repository after a certain long interval

      Workaround

      Removing the affected repository and then perform the sync one more time

            Assignee:
            Unassigned
            Reporter:
            Daryl Chuah (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: