JIRA Startup Fails from application context error

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

Symptoms

JIRA fails on startup from plugins not being enabled because of a time out error.

A similar error appears in plugin start up of plugins the atlassian-jira.log:

1 2 3 4 5 6 7 2011-12-19 11:46:19,593 Timer-0 ERROR [internal.dependencies.startup.DependencyWaiterApplicationContextExecutor] Unable to create application context for [com.atlassian.streams.jira-plugin], unsatisfied dependencies: Dependency on [(objectClass=com.atlassian.gadgets.view.GadgetViewFactory)] (from bean [&gadgetViewFactory]), Dependency on [(objectClass=com.atlassian.gadgets.GadgetRequestContextFactory)] (from bean [&gadgetRequestContextFactory]) org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.streams.jira-plugin' has timed out at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:454) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:50) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:105) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462)

Cause

There is a virus scanner installed on the server which hinders the appropriate java classes to be unpacked.

Resolution

  1. Turn off any virus scanner or malware scanner on the server

  2. Restart JIRA

    ℹ️ This can also be caused by a heavy load on the server during JIRA startup. See Bundled plugin not available error thrown on Jira server login for more details.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.