JMX monitoring is memory inefficient
Issue
- Retrieving attributes of JMX beans is using a lot of heap, making it expensive to monitor. Getting a simple attribute can lead to hundreds of megabytes of garbage that needs to be collected by the garbage collector.
Environment
- JBoss Enterprise Application Platform (EAP) 6.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
