[ https://issues.redhat.com/browse/WFLY-13631?page=com.atlassian.jira.plugi... ] Jens Borrmann updated WFLY-13631: --------------------------------- Description: We want to make use of Microprofile Health in our applications. These are deployed as EARs (due to customers' demand). HealthChecks from WARs within EARs are not displayed when accessing the health endpoint ([http://localhost:9990/health]) With a simple example (such as [https://www.adam-bien.com/roller/abien/entry/simplest_possible_microprofi...]) I have the following situation * Deploying as a WAR: Everything works fine * Deploying as an EAR (containing the WAR) the following information is displayed: {"status":"UP","checks":[\{"name":"ready-deployment.myapp.ear.microprofile.war","status":"UP"}]} Remarks: * Using the new and not deprecated /health/ready does not change anything * Using OpenLiberty everything works fine was: We want to make use of Microprofile Health in our applications. These are deployed as EARs (due to customers' demand). HealthChecks from WARs within EARs are not displayed when accessing the health endpoint ([http://localhost:9990/health]) With a simple example (such as [https://www.adam-bien.com/roller/abien/entry/simplest_possible_microprofi...]) I have the following situation * Deploying as a WAR: Everything works fine * Deploying as an EAR (containing the WAR) the following information is displayed: {{{{{"status":"UP","checks":[ \{"name":"ready-deployment.myapp.ear.microprofile.war","status":"UP"}}} {{]}}} }} Remarks: * Using the new and not deprecated /health/ready does not change anything * Using OpenLiberty everything works fine -- This message was sent by Atlassian Jira (v7.13.8#713008)