-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
High
-
None
-
Affects Version/s: JCMA - 1.12.23
-
Component/s: Jira - Migration Assistant - Export
-
None
-
19
-
Severity 3 - Minor
-
510
Issue Summary
JCMA logs export error logs in the below directory even when there are pre-checks/Migration happening on the server.
/opt/jira/jira_data/export/migration-to-cloud/dummyMigrationScopeId/log
We also see JCMA using high CPU and Memory usage due to this.
The Export errors logged are general export errors which should be logged only when the pre-checks are running.
com.atlassian.jira.migration.export.framework.ExportException: The workflow: [Aenderung (v.1222)] transition: [Create] has unsupported custom field reference in config hidFieldsList for workflow rule validator [FieldsRequiredValidator]
at com.atlassian.jira.migration.export.core.workflow.SwfExportFacadeKt.handleRuleValidationFailures(SwfExportFacade.kt:246)
at com.atlassian.jira.migration.export.core.workflow.SwfExportFacadeKt.exportWorkflowRule(SwfExportFacade.kt:236)
at com.atlassian.jira.migration.export.core.workflow.Validator$Internal.export(SwfValidatorExportService.kt:77)
at com.atlassian.jira.migration.export.core.workflow.SwfExportFacadeKt.handleRuleValidationFailures(SwfExportFacade.kt:246)
We see the below error message in Jira-Migration.log continuously.
2025-02-19 03:49:13,125 Caesium-1-4 WARN ServiceRunner [migration.analytics.errordispatcher.ExportErrorDispatcher] Error while processing migration error logs java.lang.IllegalArgumentException: Invalid UUID string: dummyMigrationScopeId at java.util.UUID.fromString(UUID.java:194) ~[?:1.8.0_402] at com.atlassian.migration.api.MigrationScopeId.<init>(MigrationScopeId.java:16) ~[plugin.3239179777832057743.jira-migration-plugin-1.12.23.jar:?] at com.atlassian.jira.migration.analytics.errordispatcher.ScopeExportErrorUploader.uploadErrorToMCS(ScopeExportErrorUploader.kt:42) ~[plugin.3239179777832057743.jira-migration-plugin-1.12.23.jar:?] at com.atlassian.jira.migration.analytics.errordispatcher.ExportErrorDispatcher.sendEventAndClean(ExportErrorDispatcher.kt:41) ~[plugin.3239179777832057743.jira-migration-plugin-1.12.23.jar:?] at com.atlassian.jira.migration.analytics.errordispatcher.ExportErrorDispatcher.handleEvents(ExportErrorDispatcher.kt:32) ~[plugin.3239179777832057743.jira-migration-plugin-1.12.23.jar:?] at com.atlassian.jira.migration.analytics.errordispatcher.ExportErrorDispatcher.processExportErrors(ExportErrorDispatcher.kt:25) ~[plugin.3239179777832057743.jira-migration-plugin-1.12.23.jar:?] at com.atlassian.jira.migration.analytics.errordispatcher.ExportErrorJobManager.runJob(ExportErrorJobManager.kt:55) ~[plugin.3239179777832057743.jira-migration-plugin-1.12.23.jar:?] at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:134) ~[?:?] at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:106) ~[?:?] at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:90) ~[?:?] at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:500) ~[?:?] at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob(CaesiumSchedulerService.java:495) ~[?:?] at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJobWithRecoveryGuard(CaesiumSchedulerService.java:519) ~[?:?] at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:415) ~[?:?] at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:66) ~[?:?] at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:60) ~[?:?] at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:35) ~[?:?] at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_402]
Steps to Reproduce
We have tried replicating the issue in the Lab, however unable to replicate the issue.
<product name="Jira" version="9.12.2" license-type="server"/> <name>Jira Cloud Migration Assistant</name> <version>1.12.23</version>
Expected Results
JCMA should stop logging export error messages after the Pre-checks/Migration is completed.
Actual Results
JCMA logs Export error messages every 10 minutes and user high CPU/RAM even when there is no activity.
Workaround
- Stop the JIRA
- Take backup and delete the records from this table (no active migration should be running this time)
Note: Only the contents from the table and not the table. - Start Jira and create a new migration plan.