-
Bug
-
Resolution: Fixed
-
High
-
None
-
JCMA - 1.12.0, JCMA - 1.12.2, JCMA - 1.12.3, JCMA - 1.12.4, JCMA - 1.12.6, JCMA - 1.12.7
-
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
- Create a migration
- 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
- is related to
-
MIG-2033 JCMA Preflights: Migrating filters with JCMA resulted in OOM
-
- Closed
-
-
MIG-1187 JCMA Preflights: JCMA Pre-flight check for "Data preparation" takes a long time to complete
- Under Consideration
- relates to
-
MIG-2042 JCMA Preflights: All filters are always being processed for every plan with Filters and Boards option
- Gathering Interest
-
ACE-6219 Loading...
- Wiki Page
-
Wiki Page Loading...
(4 mentioned in, 1 Wiki Page)