Details
-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
EAP-XP-4.0.0.CR2
-
None
-
False
-
None
-
False
-
Description
This issue is marked as blocker because it's a regression;
The "/health/ready" end-point produces the following invalid JSON (it's a JSON array instead of the usual JSON object and it doesn't contain the checks property):
[{"name" : "deployments-status", "outcome" : false},{"name" : "boot-errors", "outcome" : false},{"name" : "server-state", "outcome" : false},{ "outcome" : false }]
Scenario:
EAP is configured as described in Global status when probes are not defined;
On EAP, an application is deployed which contains just a liveness probe: no readiness health check;
While the application is deployed and probes are not yet ready you can see the a single response with code HTTP 503 which JSON body is different form all the subsequent responses which also return code HTTP 503: it's the first response after the initial HTTP 404 responses;
We provide both 7.4.4.GA-xp-4.0.0-7.4.4-CR1 and 7.4.3.GA-xp-4.0.0.GA-CR2 for comparison:
7.4.4.GA-xp-4.0.0-7.4.4-CR1
13:53:50,590 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "DelayedLivenessHealthCheck.war" (runtime-name: "DelayedLivenessHealthCheck.war")
13:53:50,603 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) WFLYDS0013: Started FileSystemDeploymentService for directory /home/hudson/hudson_workspace/workspace/eap-74x-microprofile-testsuite/8ea65e6a/microprofile-health/target/jboss-manual/deployments
HTTP 404, responseContent-1: <html><head><title>Error</title></head><body>404 - Not Found</body></html>
13:53:50,841 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:18443
HTTP 404, responseContent-2: <html><head><title>Error</title></head><body>404 - Not Found</body></html>
HTTP 503, responseContent-3: [{"name" : "deployments-status", "outcome" : false},{"name" : "boot-errors", "outcome" : false},{"name" : "server-state", "outcome" : false},{ "outcome" : false }]
13:53:50,980 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
HTTP 503, responseContent-4: {"status":"DOWN","checks":[{"name":"boot-errors","status":"DOWN"},{"name":"empty-readiness-checks","status":"DOWN"},{"name":"server-state","status":"DOWN"},{"name":"deployments-status","status":"DOWN"}]}
HTTP 503, responseContent-5: {"status":"DOWN","checks":[{"name":"boot-errors","status":"DOWN"},{"name":"empty-readiness-checks","status":"DOWN"},{"name":"server-state","status":"DOWN"},{"name":"deployments-status","status":"DOWN"}]}
HTTP 503, responseContent-6: {"status":"DOWN","checks":[{"name":"boot-errors","status":"DOWN"},{"name":"empty-readiness-checks","status":"DOWN"},{"name":"server-state","status":"DOWN"},{"name":"deployments-status","status":"DOWN"}]}
7.4.3.GA-xp-4.0.0.GA-CR2
15:53:27 13:53:26,539 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "DelayedLivenessHealthCheck.war" (runtime-name: "DelayedLivenessHealthCheck.war")
HTTP 404, responseContent-1: <html><head><title>Error</title></head><body>404 - Not Found</body></html>
13:53:27,062 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:18443
HTTP 503, responseContent-2: {"status":"DOWN","checks":[{"name":"deployments-status","status":"DOWN"},{"name":"empty-readiness-checks","status":"DOWN"},{"name":"server-state","status":"DOWN"},{"name":"boot-errors","status":"DOWN"}]}
HTTP 503, responseContent-3: {"status":"DOWN","checks":[{"name":"deployments-status","status":"DOWN"},{"name":"empty-readiness-checks","status":"DOWN"},{"name":"server-state","status":"DOWN"},{"name":"boot-errors","status":"DOWN"}]}
HTTP 503, responseContent-4: {"status":"DOWN","checks":[{"name":"deployments-status","status":"DOWN"},{"name":"empty-readiness-checks","status":"DOWN"},{"name":"server-state","status":"DOWN"},{"name":"boot-errors","status":"DOWN"}]}
HTTP 503, responseContent-5: {"status":"DOWN","checks":[{"name":"deployments-status","status":"DOWN"},{"name":"empty-readiness-checks","status":"DOWN"},{"name":"server-state","status":"DOWN"},{"name":"boot-errors","status":"DOWN"}]}
13:53:27,280 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
HTTP 503, responseContent-6: {"status":"DOWN","checks":[{"name":"deployments-status","status":"DOWN"},{"name":"empty-readiness-checks","status":"DOWN"},{"name":"server-state","status":"DOWN"},{"name":"boot-errors","status":"DOWN"}]}
HTTP 503, responseContent-7: {"status":"DOWN","checks":[{"name":"deployments-status","status":"DOWN"},{"name":"empty-readiness-checks","status":"DOWN"},{"name":"server-state","status":"DOWN"},{"name":"boot-errors","status":"DOWN"}]}
HTTP 503, responseContent-8: {"status":"DOWN","checks":[{"name":"deployments-status","status":"DOWN"},{"name":"empty-readiness-checks","status":"DOWN"},{"name":"server-state","status":"DOWN"},{"name":"boot-errors","status":"DOWN"}]}
Attachments
Issue Links
- relates to
-
-
- Verified
-