Details
-
Bug
-
Resolution: Done
-
Major
-
24.0.0.Final
-
None
-
-
Undefined
Description
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.
Attachments
Issue Links
- clones
-
JBEAP-22294 MP Health property mp.health.default.readiness.empty.response is not respected
- Resolved
- is cloned by
-
JBEAP-22366 MP Health property mp.health.default.readiness.empty.response is not respected
- Verified