23 Nov 2023 01:04 AM
Good afternoon, community.
We're experiencing an issue while trying to monitor JBoss services. The status remains “pending” despite having restarted the service. Any idea what might be causing this?
Solved! Go to Solution.
23 Nov 2023 07:48 AM
The JBoss connection pools extension is a JMX in EF2 extension, and therefore it requires the JMX 2.0 OneAgent feature to be enabled:
Apart from that, make sure to restart the machine and the process after enabling both the feature and the extension. If it's still stuck on Pending, make sure there is actually a JBoss process running on your host and that said process has the required MBeans that the extension fetches, which are under the jboss.as domain. You can check this with an MBean dump of the process or through the JMX configuration wizard directly in Dynatrace:
24 Nov 2023 03:57 PM
Thank you very much, it was a matter of waiting for the services to restart since these services restart at dawn, one more question: what is the difference between the extension: Connection Pools: JBoss and Wildfly, that is, one complements or replaces the other .
24 Nov 2023 05:57 PM
They complement each other, as one captures data only for the connection pools to databases and the other captures data related to the application server and its performance.
11 Sep 2026 10:52 PM
Hi, Reviving this thread.
What can I check other than these, on why this is still not detected?
We already restarted the JBoss Process/Service.
21 Sep 2026 08:51 AM
There's multiple things to check, the most common if you've restarted the process after enabling the extension, and if the expected MBeans are exposed by your processes so that the extension can fetch them. You could always open a support ticket with Dynatrace so we can take a closer look at the environment itself and try to figure it out for you.
Featured Posts