Add-ons cannot be enabled due to "java.lang.IllegalStateException: The bundle is uninstalled" exception
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Some add-ons cannot be enabled, like on example screenshot below:
Environment
Jira 8.x , 9.x
Diagnosis
Looking into the atlassian-jira.log files, we see the following error (example - problematic add-on is Automation for Jira):
2022-07-15 13:40:06,881+0200 ThreadPoolAsyncTaskExecutor::Thread 25 ERROR someuser 820x6456410x1 1ffgnv8 10.56.208.236,127.0.0.1 /rest/plugins/1.0/com.codebarrel.addons.automation-key [c.a.p.osgi.factory.OsgiPlugin] Unable to start the plugin container for plugin 'com.codebarrel.addons.automation'
org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from URL [bundle://260.0:0/META-INF/spring/plugin-context.xml]; nested exception is java.lang.IllegalStateException: The bundle is uninstalled.
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:417)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:338)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310)
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:196)
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:232)
...Cause
Usually, this situation occurs when add-ons attempt to read their startup dependencies from stale caches, therefore a simple Jira restart should clear this issue.
Solution
Restart Jira and check if the add-on is now enabled.
If the problem still persists, please reach out to Atlassian Support and provide the latest support zip so we could start the investigation right away.