Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-64905

Plugin default timeout value not large enough, due to this JIRA can fail to start

XMLWordPrintable

      Problem

      Upon startup, the following error is thrown in the logs:

      JIRA Startup Failed
 
You cannot access JIRA at present. Look at the table below to identify the reasons:
 
Description
 
The following plugins are required by JIRA, but have not been started:
 
* Atlassian JIRA - Plugins - Project Config Plugin (com.atlassian.jira.jira-project-config-plugin)
* Embedded Gadgets Plugin (com.atlassian.gadgets.embedded)

      This happens because the default plugin timeout limit is set too low (60 seconds). This is not always enough to load plugins into memory on lower resourced/scaling instances.

      Workaround

      Add the JVM parameter -Datlassian.plugins.enable.wait=300

      More on this here: https://confluence.atlassian.com/jirakb/troubleshooting-jira-startup-failed-error-394464512.html

            [JRASERVER-64905] Plugin default timeout value not large enough, due to this JIRA can fail to start

            Dastin Kuwałek [SoftwarePlant] added a comment -

            Does this mean that installing Jira Software version 7.4 will out of the box set up the plugin timeout to 300 seconds?

            Dastin Kuwałek [SoftwarePlant] added a comment - Does this mean that installing Jira Software version 7.4 will out of the box set up the plugin timeout to 300 seconds?

            Phillip Ponzer [Cprime] added a comment -

            Thanks!

            Phillip Ponzer [Cprime] added a comment - Thanks!

            Michael Andreacchio added a comment -

            As a resolution the workaround was put into Jira as a default setting from 7.4, ie:

            DEFAULT_ATLASSIAN_PLUGINS_ENABLE_WAIT_SECONDS = "300";

            Michael Andreacchio added a comment - As a resolution the workaround was put into Jira as a default setting from 7.4, ie: DEFAULT_ATLASSIAN_PLUGINS_ENABLE_WAIT_SECONDS = "300" ;

            Phillip Ponzer [Cprime] added a comment -

            We know what the workaround is, but what's the resolution?

            Phillip Ponzer [Cprime] added a comment - We know what the workaround is, but what's the resolution?

              mrzymski Maciej Rzymski
              mandreacchio Michael Andreacchio
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: