# No JMX metrics in JBoss EAP 7.3.0

**URL:** <https://discuss.elastic.co/t/no-jmx-metrics-in-jboss-eap-7-3-0/238438>\
**Category:** APM\
**Tags:** java\
**Created:** [June 24, 2020, 10:52am UTC](https://discuss.elastic.co/t/no-jmx-metrics-in-jboss-eap-7-3-0/238438 "2020-06-24T10:52:16Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![Sylvain\_Juge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sylvain_juge/32/55521_2.png) [@Sylvain\_Juge](https://discuss.elastic.co/u/Sylvain_Juge)\
**Post date:** [July 2, 2020, 1:08pm UTC](https://discuss.elastic.co/t/no-jmx-metrics-in-jboss-eap-7-3-0/238438/14 "2020-07-02T13:08:56Z")

</div>

We found a way to make it work, could you try [this snapshot](https://apm-ci.elastic.co/job/apm-agent-java/job/apm-agent-java-mbp/job/PR-1258/lastSuccessfulBuild/artifact/src/github.com/elastic/apm-agent-java/elastic-apm-agent/target/elastic-apm-agent-1.17.1-SNAPSHOT.jar) to check if it's now working as expected ?

The underlying issue is that Jboss does not seem to always trigger notifications for beans that are in the `boss.as` domain, but if you configure it with `jboss.as.expr` it should work. The fix in the snapshot just applies a fallback to detect when the bean is added, so you just can use the beans as you see them in `jconsole`.

---

_[View the full topic](https://discuss.elastic.co/t/no-jmx-metrics-in-jboss-eap-7-3-0/238438)._