-
Bug
-
Resolution: Won't Do
-
Critical
-
None
Starting from Wildfly 19 Beta 2 and with current feature branch for MP Health upgrade to 2.2 [1], some tests started to fail, reporting unexpected content in JSON response.
When no readiness health check procedures are defined for a given deployment - the returned JSON payload contains a "default" health check readiness object, conventionally named as "ready-deployment." + <archive-name>
The same does not happen when there's just one registered readiness procedure - i.e. when no annotated liveness procedures exist.
This change is not documented in the Analysis document: https://github.com/wildfly/wildfly-proposals/pull/284
The following example uses an Arquillian deployment with a single HealthCheck implementation with liveness health check procedure.
1. feature branch [1]
//health { "status": "UP", "checks": [ { "name": "live", "status": "UP", "data": { "key": "value" } }, { "name": "ready-deployment.HealthTest.war", "status": "UP" } ] } //live { "status": "UP", "checks": [ { "name": "live", "status": "UP", "data": { "key": "value" } } ] } //ready { "status": "UP", "checks": [ { "name": "ready-deployment.HealthTest.war", "status": "UP" } ] }
2. here are the results for the same calls against Wildfly 19 Beta 1:
//health { "status": "UP", "checks": [ { "name": "live", "status": "UP", "data": { "key": "value" } } ] } //live { "status": "UP", "checks": [ { "name": "live", "status": "UP", "data": { "key": "value" } } ] } //ready { "status": "UP", "checks": [] }