-
Bug
-
Resolution: Fixed
-
High
-
JCMA - 1.9.8, JCMA - 1.9.10, JCMA - 1.9.17
-
11
-
Major
-
37
Issue Summary
This is reproducible on Data Center: Yes
Steps to Reproduce
This issue was reported in the Jira Application and it was noticed during two scenarios:
- While exiting from safe mode.
- While enabling the plugin after disabling it from the Manage app (
> Manage apps) section of Jira.
Expected Results
The plugin was enabled successfully.
Actual Results
The plugin fails to enable due to the below exception.
- You will receive the below error message while exiting safe mode.
- You will receive the below error message while enabling the plugin manually.
The below exception is thrown in the application logs (atlassian-jira.log file):
ThreadPoolAsyncTaskExecutor::Thread 37 ERROR admin 817x921x1 1o5191q 172.29.185.124,172.50.0.3 /rest/plugins/1.0/com.atlassian.jira.migration.jira-migration-plugin-key [c.a.p.osgi.factory.OsgiPlugin] Unable to start the plugin container for plugin 'com.atlassian.jira.migration.jira-migration-plugin'Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'planExecutionService' defined in URL nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'fx3PluginClient' defined in URL [bundle://082c48a0-acc2-4f39-b631-a3717f32a892_259.0:1/com/atlassian/jira/migration/fx3/Fx3PluginClient.class]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.atlassian.jira.migration.fx3.Fx3PluginClient]: Constructor threw exception; nested exception is java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@23ff3a8a[Not completed, task = java.util.concurrent.Executors$RunnableAdapter@356a54f8[Wrapped task = com.atlassian.fx3.Fx3Client$Companion$$Lambda$4286/0x00000008434e7840@5df81b38]] rejected from java.util.concurrent.ScheduledThreadPoolExecutor@526b62cf[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0]
Workaround
- As a temporary solution, clear the plugin cache.
- Steps to clear the Jira plugin cache:
- Stop Jira
- Delete the <jira_home>/plugins/.bundled-plugins directory
- Delete the <jira_home>/plugins/.osgi-plugins directory
- Start Jira
- Steps to clear the Jira plugin cache:
- Or until the bug is fixed replace the JCMA plugin version with a lower version ie: 1.9.7
- Uninstall the existing JCMA plugin from your Jira instance, through the Manage apps page.
- Navigate to
> Manage apps
- Search for the Jira Cloud Migration Assistant plugin.
- Click Uninstall.
- Download JCMA plugin version 1.9.7 from here
- Navigate to
> Manage apps > Upload app
- Choose the downloaded jar file and click upload.
- Navigate to
- Uninstall the existing JCMA plugin from your Jira instance, through the Manage apps page.
- causes
-
MOVE-140753 Loading...