JIRA WAR Fails to Start due to Invalid or Unreadable WAR File

Related content

  • No related content found

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

Running startup.bat / startup.sh in Tomcat/bin to start JIRA, the startup window shows up and disappears quickly.
The following appears in the Tomcat/logs/catalina.YYYY-MM-dd.log:

SEVERE: Exception fixing docBase for context [/jira621]
java.io.FileNotFoundException: <path/to/WAR/file> (The system cannot find the path specified)
	at java.util.zip.ZipFile.open(Native Method)
	at java.util.zip.ZipFile.<init>(Unknown Source)
	at java.util.jar.JarFile.<init>(Unknown Source)
	at java.util.jar.JarFile.<init>(Unknown Source)
...
SEVERE: Error starting static Resources
java.lang.IllegalArgumentException: Invalid or unreadable WAR file : <path/to/WAR/file>
...
SEVERE: A child container failed during start
java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/jira621]]
...
SEVERE: The required Server component failed to start so Tomcat is unable to start.
org.apache.catalina.LifecycleException: Failed to start component [StandardServer[2345]]
...
WARNING: Failed to retrieve JNDI naming context for container [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/jira621]] so no cleanup was performed for that container
javax.naming.NamingException: No naming context bound to this class loader

Cause

  1. The WAR file might not have been built.
  2. The WAR file might have become corrupted.
  3. The WAR file might have been moved to somewhere else and the docBase attribute in Tomcat/conf/server.xml is pointing to an invalid path.

Resolution

  1. Build the WAR file by running JIRA_WAR/build.bat (Windows) or JIRA_WAR/build.sh (Linux).
  2. Rebuild the WAR file by following these steps:
    • Delete the folders dist-generic, dist-tomcat, tmp from JIRA_WAR directory
    • Run JIRA_WAR/build.bat (Windows) or JIRA_WAR/build.sh (Linux)
  3. Check Tomcat/conf/server.xml and make sure the docBase attribute (inside Context tag) is pointing to a valid path (usually JIRA_WAR/dist-generic/atlassian-jira-x.y.z.war).
Last modified on Apr 7, 2016

Was this helpful?

Yes
No
Provide feedback about this article

Related content

  • No related content found
Powered by Confluence and Scroll Viewport.