The Jira process starts but cannot be accessed, no output in atlassian-jira.log

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Server and Data Center Only - This article only applies to Atlassian products on the server and data center platforms.


The Jira process can be start and stopped but Jira itself is inaccessible while nothing is ever written to atlassian-jira.log

The following appears in the catalina.log on Linux or jirasoftware(service-id)-stderr.(date).log on Windows

24-May-2019 10:25:06.431 SEVERE [localhost-startStop-1] org.apache.catalina.startup.ContextConfig.configureStart Marking this application unavailable due to previous error(s)
24-May-2019 10:25:06.434 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal One or more components marked the context as not correctly configured
24-May-2019 10:25:06.448 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/] startup failed due to previous error


web.xml, located under the conf directory in the Jira installation folder, is invalid.


Review web.xml and fix the discrepancy. If nothing is immediately obvious download the Jira installer zip file and copy the standard web.xml file into the conf directory.

Last modified on Nov 23, 2020

Was this helpful?

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