Summary

When JIRA starts up, it goes through several phases, any start-up errors detected after the bootstrap component container is initialised and before the full pico container is initialised are not currently displayed correctly in the UI ( a meaningful error page) and a 500 response is returned instead.

As a consequence, the administrator needs to parse through the logs and review stack-traces to understand the nature of the start-up error.

Steps to Reproduce

• Set up a JIRA instance.
• Modify your database credentials via dbconfig.xml to be incorrect.
• Start up JIRA
• Go to JIRA (http(s)://<instance-url>/jira)

Actual Results

• A 500 response is returned to the browser and a blank page describing that the there was rendering issue whilst attempting to display the page referring the user to the logs for more information.
• The logs are filled with exceptions related to both issues retrieving JIRA components and database connection failing to be established.

Expected Results

• The standard error page (Johnson) is displayed correctly, indicating that JIRA is locked for use and that an start-up error has occurred.
• The logs only have exception output related to the database mis-configuration

Workaround

• Please refer to the logs and review the output of the stacktraces related to the database misconfiguration so the credentials can be corrected.