[
https://issues.redhat.com/browse/WFLY-12835?page=com.atlassian.jira.plugi...
]
charles ghislain edited comment on WFLY-12835 at 5/6/20 11:24 AM:
------------------------------------------------------------------
It affects 19.0.0.Final as well.
The org.wildfly.extension.microprofile.health.deployment.CDIExtension resolves
HealthChecks using 'Weld BeanManager for
org.wildfly.extension.microprofile.health-smallrye.additionalClasses [bean count=32]'
wich does not find Healtcheck present in ejbs or wars modules of an ear.
Using CDI.current() there works, but is not reliable for ear if im not mistaken.
On Wildfly 16 application checks are discovered with the same setup
was (Author: cghislai):
It affects 19.0.0.Final as well.
The org.wildfly.extension.microprofile.health.deployment.CDIExtension resolves
HealthChecks using 'Weld BeanManager for
org.wildfly.extension.microprofile.health-smallrye.additionalClasses [bean count=32]'
wich does not find Healtcheck present in ejbs or wars modules of an ear.
Using CDI.current() there works, but is not reliable for ear if im not mistaken.
Im sure it worked with earlier versions, before the change in the output json schema.
HealthChecks in subdeployments are not registered
-------------------------------------------------
Key: WFLY-12835
URL:
https://issues.redhat.com/browse/WFLY-12835
Project: WildFly
Issue Type: Feature Request
Components: MP Health
Affects Versions: 18.0.1.Final
Reporter: Ivan Straka
Assignee: Jeff Mesnil
Priority: Critical
After EAR is deployed HealthChecks are not registered and not exposed under _/health_
endpoint.
EAR contains one WAR and one JAR. Both of them contains HealthChecks.
Test source:
https://github.com/istraka/eap-microprofile-test-suite/blob/mp-health/mic...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)