Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-46156

PICO thread safety race condition on JIRA backup restore in Cloud

XMLWordPrintable

    • Severity 3 - Minor
    • Hide
      Atlassian Update – 3 November 2017

      Hi everyone,

      The issue has not get additional interest since the time it has been reported. Additionally it lacks important information as an affected version, etc.

      Therefore I'm resolving the issue as Timed out.

      Atlassian will continue to watch issue for the further updates, so please don't hesitate to share your feedback in the issue comments.

      Cheers,
      Ignat Alexeyenko
      Jira bugmaster.

      Show
      Atlassian Update – 3 November 2017 Hi everyone, The issue has not get additional interest since the time it has been reported. Additionally it lacks important information as an affected version, etc. Therefore I'm resolving the issue as Timed out . Atlassian will continue to watch issue for the further updates, so please don't hesitate to share your feedback in the issue comments. Cheers, Ignat Alexeyenko Jira bugmaster.

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

      This bug is caused by a race condition.

      Steps to reproduce:
      Login to JIRA Cloud instance restore a JIRA Backup. Since this is a race condition, we may have to repeat the restore process few times.

      In the process of restoring a JIRA backup onto this instance, it had imported the data, it was on the way of disabling/enabling the add-ons, and I hit this stacktrace: https://bitbucket.org/snippets/atlassian/zLr9X

      Full log file attached

        1. jira.log
          1.56 MB

              Unassigned Unassigned
              ccapiaux Clement Capiaux (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: