JIRA WAR install does not start with error "Running JIRA from a packed WAR is not supported"

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

When JIRA is started, it becomes locked due to a fatal error during bootstrapping.

The following appears in the atlassian-jira.log:

2013-12-11 16:11:19,502 localhost-startStop-1 FATAL      [atlassian.jira.startup.BootstrapContainerLauncher] A fatal error occurred during bootstrapping. JIRA has been locked.
java.lang.IllegalStateException: Running JIRA from a packed WAR is not supported. Configure your Servlet container to unpack the WAR before running it. (Cannot resolve real path for '/WEB-INF/atlassian-bundled-plugins')
	at com.atlassian.jira.plugin.PluginFactoryAndLoaderRegistrar.getBundledPluginsLoader(PluginFactoryAndLoaderRegistrar.java:139)
	at com.atlassian.jira.plugin.BootstrapPluginLoaderFactory.getPluginLoaders(BootstrapPluginLoaderFactory.java:68)
	at com.atlassian.jira.plugin.JiraPluginManager.<init>(JiraPluginManager.java:67)

Cause

JIRA does not support running from a packed WAR. This will be caused by a setting similar to the below example in Tomcat's server.xml:

<Host name="localhost" appBase="webapps" unpackWARs="false" autoDeploy="true">

Resolution

  • You should set "unpackWARs=true" in server.xml, for example:

    <Host name="localhost" appBase="webapps" unpackWARs="true" autoDeploy="true">

    (info) The "Host" element may have exactly the same attributes as above, the important thing is that "unpackWARs" must be set to "true".

Last modified on Mar 30, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.