Apps cannot be enabled due to a system plugin not resolving
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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
After rolling back an upgrade, enabling certain third party apps result in a hanging page. The apps are not enabled properly.
Diagnosis
Upon checking the application logs, there are error entries where the plugin cannot be enabled because of a missing system class.
In the example below, the com.pyxis.greenhopper.jirasystem class for Jira boards is not loaded properly and shows up as missing when trying to enable a third party app.
1
Caused by: org.osgi.framework.BundleException: Unable to resolve com.easyagile.programs [198](R 198.0): missing requirement [com.easyagile.programs [198](R 198.0)] osgi.wiring.package; (osgi.wiring.package=com.atlassian.greenhopper.service.sprint) [caused by: Unable to resolve com.pyxis.greenhopper.jira [207](R 207.0): missing requirement [com.pyxis.greenhopper.jira [207](R 207.0)] osgi.wiring.package; (&(osgi.wiring.package=com.atlassian.jira.i18n.terminology)(version>=7.0.0))] Unresolved requirements: [[com.easyagile.programs [198](R 198.0)] osgi.wiring.package; (osgi.wiring.package=com.atlassian.greenhopper.service.sprint)]
Cause
When rolling back an upgrade, stray Jira JAR files in the <shared_home>/plugins/installed-plugins directory can cause confusion during startup.
For example, when there is a cancelled upgrade from 8.13.x to 8.20.x, the JAR files from 8.20.x will remain in the <shared_home>/plugins/installed-plugins directory.
If the 8.20.x JAR files are not removed, they will be loaded during the startup of the 8.13.x Jira instance and cause errors during normal operations of the Jira instance.
Solution
Remove all JAR files that are not of the current Jira instance version from the
<shared_home>/plugins/installed-pluginsdirectory.Clear the local plugin caches.
Restart Jira.
Was this helpful?