Issue Summary

CustomisedConfigurationsHealthCheck failed, the instance showed Johnson page about modifications in setenv.sh. Any request issued to the instance ended with HTTP 503. Meanwhile, querying "/status" endpoint returned "Running" status. 

Steps to Reproduce

1. Modify the HealthCheck to always fail
2. See the Johnson page or issue a REST call
3. query the "/status" endpoint

Expected Results

When Johnson page is shown and the instance is not working, /status should never return a "RUNNING" state.

Actual Results

// 20191211194005
// https://jira-localhost/status{
  "state": "RUNNING"
}

Workaround

I don't think there's a stable workaround. Technically, one could ping an endpoint other than /status, but that would possibly break under other circumstances.