Intermittent Jira startup issues on Jira 8.20.2 and above using Java 11.
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
Jira startup fails intermittently as all the required system plugins fail to start due to timeout.
Environment
Jira version 8.20.2 and above using Java 11
Diagnosis
Jira Application Logs (atlassian-jira.log) show the following behavior:
Plugin Initialization timeout:
2022-05-09 09:38:52,281+0200 Spring DM Context Creation Timer WARN [o.e.g.b.e.i.dependencies.startup.DependencyWaiterApplicationContextExecutor] Timeout occurred before finding service dependencies for [NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.gadgets.directory, config=osgibundle:/META-INF/spring/*.xml)]
2022-05-09 09:38:52,281+0200 Spring DM Context Creation Timer ERROR [c.a.p.osgi.factory.OsgiPlugin] Plugin 'com.atlassian.gadgets.directory' never resolved service '&subscribedGadgetFeedStore' with filter '(&(objectClass=com.atlassian.gadgets.directory.spi.SubscribedGadgetFeedStore)(objectClass=com.atlassian.gadgets.directory.spi.SubscribedGadgetFeedStore))'
2022-05-09 09:38:52,281+0200 Spring DM Context Creation Timer ERROR [c.a.p.osgi.factory.OsgiPlugin] Unable to start the plugin container for plugin 'com.atlassian.gadgets.directory'
org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.gadgets.directory' has timed out waiting for (&(objectClass=com.atlassian.gadgets.directory.spi.SubscribedGadgetFeedStore)(objectClass=com.atlassian.gadgets.directory.spi.SubscribedGadgetFeedStore))
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
at java.base/java.util.TimerThread.mainLoop(Timer.java:556)
at java.base/java.util.TimerThread.run(Timer.java:506)
2022-05-09 09:38:52,437+0200 Spring DM Context Creation Timer WARN [o.s.b.factory.support.DisposableBeanAdapter] Invocation of destroy method failed on bean with name 'dashboardItemModulesList': java.lang.NullPointerException
2022-05-09 09:38:52,437+0200 Spring DM Context Creation Timer WARN [o.s.b.factory.support.DisposableBeanAdapter] Invocation of destroy method failed on bean with name 'localGadgetSpecProviders': java.lang.NullPointerException
2022-05-09 09:38:52,437+0200 Spring DM Context Creation Timer WARN [o.s.b.factory.support.DisposableBeanAdapter] Invocation of destroy method failed on bean with name 'gadgetSpecProviders': java.lang.NullPointerException
2022-05-09 09:38:52,453+0200 Spring DM Context Creation Timer ERROR [o.e.g.b.e.internal.support.ExtenderConfiguration] Application context refresh failed (NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.gadgets.directory, config=osgibundle:/META-INF/spring/*.xml))
org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.gadgets.directory' has timed out waiting for (&(objectClass=com.atlassian.gadgets.directory.spi.SubscribedGadgetFeedStore)(objectClass=com.atlassian.gadgets.directory.spi.SubscribedGadgetFeedStore))
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
at java.base/java.util.TimerThread.mainLoop(Timer.java:556)
at java.base/java.util.TimerThread.run(Timer.java:506)Followed by Jira startup failure due to the above timeouts occurring for required system plugins.
2022-05-09 09:40:22,005+0200 JIRA-Bootstrap ERROR [c.a.jira.startup.SystemPluginsEnabledHealthCheck] We couldn't start the following plugins:
- Jira Projects Plugin (com.atlassian.jira.jira-projects-plugin)
- Gadget Directory Plugin (com.atlassian.gadgets.directory)
- Atlassian Jira - Plugins - Gadgets Plugin (com.atlassian.jira.gadgets)
- Atlassian Jira - Plugins - Global Issue Navigator (com.atlassian.jira.jira-issue-nav-plugin)
- Atlassian JIRA - Plugins - Quick Edit Plugin (com.atlassian.jira.jira-quick-edit-plugin)
- Atlassian Jira - Plugins - REST Plugin (com.atlassian.jira.rest)
- atlassian-servlet-plugin (com.atlassian.web.atlassian-servlet-plugin)
2022-05-09 09:40:26,005+0200 JIRA-Bootstrap ERROR [c.a.jira.startup.DefaultJiraLauncher] JIRA has failed to start because of the following errors: [(Event: Level = (EventLevel: fatal) , Key =
(EventType: system-plugins) , Desc = We haven't been able to start all the required system plugins , Exception = We couldn't start the following plugins:<br/><ul><li>Jira Projects Plugin
(com.atlassian.jira.jira-projects-plugin)</li><li>Gadget Directory Plugin (com.atlassian.gadgets.directory)</li><li>Atlassian Jira - Plugins - Gadgets Plugin (com.atlassian.jira.gadgets)</li>
<li>Atlassian Jira - Plugins - Global Issue Navigator (com.atlassian.jira.jira-issue-nav-plugin)</li><li>Atlassian JIRA - Plugins - Quick Edit Plugin (com.atlassian.jira.jira-quick-edit-plugin)</li>
<li>Atlassian Jira - Plugins - REST Plugin (com.atlassian.jira.rest)</li></ul>)]Cause
The root causes are being tracked under the below Jira Bug:
JRASERVER-73257: Plugins fail to start in Jira 8.20 with Java 11.x
Solution
Please track JRASERVER-73257 for a fix. The status of the Bug is in "In Progress" while writing this article and it will be fixed as per our Atlassian Server bug fix policy.
Workaround
The startup issue is occurring due to multiple root causes. Below are the workarounds which help in fixing some of the known root causes.
A) Upgrade atlassian-servlet-plugin to v. 6.0.1
Note: "atlassian-servlet-plugin" version 6.0.1 comes bundled with Jira 9.0.0, 8.22.3, 8.20.10. If you have an older version of the "atlassian-servlet-plugin", you can follow the below steps to update it.
Download "atlassian-servlet-plugin" version 6.0.1. (available as an attachment at the bug JRASERVER-73257).
Follow the "Updating apps by file upload" method in updating apps KB to update atlassian-servlet-plugin.
If "atlassian-servlet-plugin" update does not help:
B) Upgrade atlassian-servlet-plugin to v. 6.0.1 AND atlassian-authentication-plugin to 4.2.12
Upgrade the "atlassian-servlet-plugin" using steps mentioned in workaround A.
Upgrade the "atlassian-authentication-plugin" using the steps below.
Shut down Jira.
Replace the existing "atlassian-authentication-plugin" from $JIRA_INSTALL/atlassian-jira/WEB-INF/atlassian-bundled-plugins with atlassian-authentication-plugin-4.2.12.jar, available to download at JRASERVER-73257.
Start Jira.
If both workaround A and B do not help:
C) Switch the Java version to Java 8
Note: Java 8 requires a few flags that are not supported in Java 11. When switching to Java 8, these flags should be included. Additional information can be found in the following article:
Was this helpful?