-
Bug
-
Resolution: Done
-
Critical
-
EAP-XP-3.0.0.CR2
-
False
-
False
-
-
-
-
-
-
Undefined
-
-
-
The MP Health spec uses mp.health.default.readiness.empty.response to define empty readiness response when the server is starting and the deployments are not yet processed so it won't respond up to /health/ready before the user readiness checks are processed. This is currently done through management model `empty-readiness-checks-status` attribute which adds and empty readiness health check with the correct status. However, when the user specifies also `mp.health.disable-default-procedures=true` this will remove the mentioned health check and the server responds UP before the user checks can be processed.
- clones
-
JBEAP-22366 MP Health property mp.health.default.readiness.empty.response is not respected
- Closed
- is cloned by
-
WFLY-15070 MP Health property mp.health.default.readiness.empty.response is not respected
- Closed
- is related to
-
JBEAP-23249 Possible intermittent failures in MicroProfileHealthDefaultEmpty*HTTPEndpointTestCases in XP
- Closed
- relates to
-
JBEAP-23076 MP Health subsytem property empty-startup-checks-status is not included in default configuration
- Closed