Development panel breaks if Bamboo is unreachable during sync process

XMLWordPrintable

    • Type: Bug
    • Resolution: Answered
    • Priority: Low
    • None
    • Affects Version/s: 8.9.1
    • Component/s: Development Panel
    • 8.09
    • 11
    • Severity 3 - Minor
    • 2

      Issue Summary

      If there are connection issues between Jira and Bamboo during real-time or background sync process, the development panel can become corrupt and all Jira issues that have Bamboo build info associated with them will be missing from the development panel.

      Steps to Reproduce

      1. Link a build to an issue
      2. Deploy the build
      3. Interrupt the application link by stopping Bamboo or by other methods

      Expected Results

      The application link would gracefully handle the loss of connection and refresh the cache once the connection is restored

      Actual Results

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

      Caesium-1-3 ERROR ServiceRunner     [c.a.j.p.devstatus.provider.DefaultDevSummaryPollService] Refresh failure
      com.atlassian.jira.plugin.devstatus.provider.DataProviderRefreshFailure: Data Provider [Id: 72eefabd-9fb6-35c2-a401-671d06c58b00, Type: bamboo] refresh failed with error code -1 and message - timeout after 10000ms, not getting from cache]
      	at com.atlassian.jira.plugin.devstatus.provider.DefaultCachingProviderHelper.refreshProvider(DefaultCachingProviderHelper.java:78)
      

      After some time, the poll service stops and the AO_575BF5_DEV_SUMMARY cache becomes stale – the result is that all Bamboo build info will be missing from the development panel in the Jira issues.

      Workaround

      Use the query below to delete the development information in the issue:

      --Query for Postgresql
      DELETE
      FROM "AO_575BF5_DEV_SUMMARY"
      WHERE "AO_575BF5_DEV_SUMMARY"."JSON" LIKE '%ISSUE-123%';
      
      --Query for other DB engines
      DELETE
      FROM AO_575BF5_DEV_SUMMARY
      WHERE AO_575BF5_DEV_SUMMARY.JSON LIKE '%ISSUE-123%';
      

      When accessing the issue again, Jira will recreate the entry in the database and will show the correct information.

            Assignee:
            Yann
            Reporter:
            Chris Terry
            Votes:
            3 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: