Jira server throws timeout errors on install or upgrade


アトラシアン コミュニティをご利用ください。



When installing or upgrading to JIRA Software, the following error may occur:

The call to the JIRA server did not complete within the timeout period. We are unsure of the result of this operation.

atlassian-jira.log に次のメッセージが表示される。

Caused by: java.lang.IllegalStateException: Can only register services while bundle is active or activating.
    at org.apache.felix.framework.Felix.registerService(Felix.java:2817)
    at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:251)


/rest/plugins/1.0/com.pyxis.greenhopper.jira-key [atlassian.plugin.manager.DefaultPluginManager] There was an error loading the descriptor 'JIRA Agile Help' of plugin 'com.pyxis.greenhopper.jira'. Disabling.
java.lang.RuntimeException: Unable to enable web fragment
    at com.atlassian.plugin.web.descriptors.AbstractWebFragmentModuleDescriptor.enabled(AbstractWebFragmentModuleDescriptor.java:133)
    at com.atlassian.plugin.web.descriptors.DefaultWebItemModuleDescriptor.enabled(DefaultWebItemModuleDescriptor.java:72)
    at com.atlassian.plugin.web.descriptors.DefaultAbstractWebFragmentModuleDescriptor.enabled(DefaultAbstractWebFragmentModuleDescriptor.java:34)
Caused by: java.lang.IllegalStateException: Cannot create object because the plugin container is unavailable for bundle 'com.pyxis.greenhopper.jira'
    at com.atlassian.plugin.osgi.factory.OsgiPluginInstalledHelper.getRequiredContainerAccessor(OsgiPluginInstalledHelper.java:219)
    at com.atlassian.plugin.osgi.factory.OsgiPlugin.autowire(OsgiPlugin.java:372)
    at com.atlassian.plugin.osgi.factory.OsgiPlugin.autowire(OsgiPlugin.java:362)



There are two known causes for this issue:

  1. The inconsistency of OSGI plugin caches triggered from inappropriate shutdown of Tomcat.
  2. The Tomcat user not have the correct permissions to access the directory.


Option #1

  1. Stop JIRA Software;
  2. Remove the below directories, that hold plug-in caches:


    (info) Those directories will be recreated upon JIRA Software's next startup.

  3. Ensure that the user which runs JIRA Software has the correct permissions on these directories (recursively);
  4. Start JIRA Software;
(info) We have a bug that is being tracked for this behaviour under JRA-27438 - Getting issue details... STATUS - please vote and watch it for future updates from our developers on a permanent solution.

Option #2

If the above solution does not work, then you're probably facing a timeout problem. To resolve that, you'll have to increase the timeout JIRA Software imposes in the plugin loading process.

  1. Stop the application JIRA Software;
  2. Following these instructions, add the below argument to JIRA Software's startup parameters:

  3. Start the application JIRA Software.
最終更新日 2019 年 9 月 25 日


Powered by Confluence and Scroll Viewport.