JCMA Preflights: Jira migration with JCMA causes out-of-memory when exporting historical data

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: High
    • None
    • Affects Version/s: JCMA - 1.12.0, JCMA - 1.12.2, JCMA - 1.12.3, JCMA - 1.12.4, JCMA - 1.12.6, JCMA - 1.12.7
    • Component/s: Viper CMAs - Australia
    • 10
    • Severity 1 - Critical
    • 197

      Issue Summary

      • Running a Jira migration with JCMA can contribute to an OOM exception in the server while exporting historical data in preflight phase.

      This is reproducible on Data Center: (yes) / (no)

      Steps to Reproduce

      1. Create a migration
      2. Run JCMA preflight checks.

      Expected Results

      • Executing the preflight checks without causing issues in the server.

      Actual Results

      • Jira server run out of memory and throw and OOM exception.

      Workaround

      • We've disabled the part of the code that's potentially causing this issue till we find the rootCause and provide fix.

      Logs to collect when issue surfaces again

      • Heap dump logs
      • Jira support logs for migration

            Assignee:
            Hung Gia Dien
            Reporter:
            Wellington Costa
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: