Issue Summary

In Jira Data Center 11.x, the /status health check endpoint returns HTTP 404 (Tomcat default error page) when the application starts in a FIRST_RUN state — i.e., when dbconfig.xml is not yet configured.

HTTP Status 404 – Not Found
Type Status Report
Description: The origin server did not find a current representation for the target resource
or is not willing to disclose that one exists. 

In Jira Data Center 10.x, the same scenario correctly returns HTTP 200 with {"state":"FIRST_RUN"}, as documented in [Jira 'status' endpoint response meanings | Jira and Jira Service Management | Atlassian Support.|https://support.atlassian.com/jira/kb/jira-status-endpoint-response-meanings/]

Note: If we started Jira without both dbconfig.xml and cluster.properties the /status will return the {"state":"FIRST_RUN"}; however, if we start Jira with cluster.properties and no dbconfig.xml, a 404 error will happen.

Steps to Reproduce

1. Install Jira Software Data Center
2. DO configure cluster.properties in JIRA_HOME
3. Do NOT configure dbconfig.xml in JIRA_HOME
4. Start Jira
5. Make a GET request to JIRA_BASEURL:<port>/status

Expected Results

HTTP 200 response with JSON body:

{"state":"FIRST_RUN"}

Actual Results

Jira 11.x returns HTTP 404 with Tomcat's default error page:

HTTP Status 404 – Not Found
Type Status Report
Description: The origin server did not find a current representation for the target resource
or is not willing to disclose that one exists.
Apache Tomcat/10.1.53

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available