Details
-
Bug
-
Resolution: Timed out
-
Low
-
None
-
8.6.0
-
8.06
-
Severity 3 - Minor
-
Description
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
- Modify the HealthCheck to always fail
- See the Johnson page or issue a REST call
- 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.
Attachments
Issue Links
- is related to
-
JRASERVER-65708 /status returns Maintenance instead of Running when nodes are not in Maintenance mode and the Database is configured with an unsupported collation
-
- Long Term Backlog
-
- relates to
-
XPLN-1361 Loading...