Jira Software and other bundled plugins will not load after startup
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
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.
*Fisheye および Crucible は除く
問題
- After Jira upgrade or migration, Jira Software and other bundled and user-installed plugins fail to load during Jira startup.
- The following symptoms are observed: “Unable to create Jira Software project.“, “Unable to use features related to user-installed plugins.”
診断
- Third-party plugin versions are compatible with the installed/upgraded Jira version
- When running the query “Select * from pluginstate;” in the Jira DB, all the plugins are ‘enabled’ (flag is set to ‘true’ in pluginstate table).
Renaming the folder <JIRA_HOME>/plugins/installed-plugins and restarting Jira so that Jira can start without any third-party plugins does not resolve the issue
The following appears in the atlassian-jira.log
'com.atlassian.jira.jira-software-application' - 'Jira Software Application' failed to load.
Cannot start plugin: com.atlassian.jira.jira-software-application
Unable to resolve com.atlassian.jira.software-application [81](R 81.0): missing requirement [com.atlassian.jira.software-application [81](R 81.0)] osgi.wiring.package; (osgi.wiring.package=com.atlassian.jira.plugins.dvcs.obr.install) [caused by: Unable to resolve com.atlassian.jira.plugins.jira-dvcs-connector-plugin [100](R 100.0): missing requirement [com.atlassian.jira.plugins.jira-dvcs-connector-plugin [100](R 100.0)] osgi.wiring.package; (osgi.wiring.package=com.atlassian.streams.api.common) [caused by: Unable to resolve com.atlassian.streams.api [175](R 175.0): missing requirement [com.atlassian.streams.api [175](R 175.0)] osgi.wiring.package; (&(osgi.wiring.package=javax.servlet.http)(version>=3.1.0))]] Unresolved requirements: [[com.atlassian.jira.software-application [81](R 81.0)] osgi.wiring.package; (osgi.wiring.package=com.atlassian.jira.plugins.dvcs.obr.install)]
--------------------------------------------------------------------------------------------------
2020-05-25 19:19:11,775+0200 FelixStartLevel WARN [o.e.g.b.e.internal.support.ExtenderConfiguration] Gemini Blueprint extensions bundle not present, annotation processing disabled.
2020-05-25 19:19:11,821+0200 FelixDispatchQueue ERROR [c.a.p.o.container.felix.FelixOsgiContainerManager] Framework error in bundle com.atlassian.platform.spring-velocity-support
org.osgi.framework.BundleException: Unable to resolve com.atlassian.platform.spring-velocity-support [17](R 17.0): missing requirement [com.atlassian.platform.spring-velocity-support [17](R 17.0)] osgi.wiring.package; (&(osgi.wiring.package=javax.servlet)(version>=3.0.0)(!(version>=4.0.0))) Unresolved requirements: [[com.atlassian.platform.spring-velocity-support [17](R 17.0)] osgi.wiring.package; (&(osgi.wiring.package=javax.servlet)(version>=3.0.0)(!(version>=4.0.0)))]
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4149)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2119)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1373)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
at java.lang.Thread.run(Thread.java:748)
- atlassian-jira.log also shows that a non-supported Tomcat version is being used:
Application Server : Apache Tomcat/7.0.76 - Servlet API 3.0
2020-05-11 04:17:05,718+0200 JIRA-Bootstrap ERROR [c.a.j.health.checks.TomcatConfigurationHealthCheck] Server Apache Tomcat/7.0.76 is not compatible with Tomcat 8.5 nor 9.0
原因
The issue is caused when the supported tomcat version is not used. For any version of Jira, only supported Apache Tomcat Application server must be used. Using any other version of Apache tomcat (previous or later versions) may cause this error.
ソリューション
Only use the supported Apache Tomcat Application server mentioned in the Supported platforms. After installing the Supported version and restarting the server, issue will be resolved.