8 Replies Latest reply on Sep 25, 2014 9:48 AM by Tomaž Cerar

    JMX monitoring is extremely memory inefficient

    Koen Janssens Newbie



      I'm using jboss EAP 6.1.1. When reading any JMX attribute(s), I have noticed a noticeable impact on the performance of our system. After attaching a profiler, I see that getting a single attribute of a JMX bean (either using remoting or using jconsole) is generating thousands of objects, that have to cleaned up by the GC. For instance, 6000 instances of the ModelNode class are created.


      A clone is made of the complete management model before executing any JMX operation. This happens in the OperationContextImpl.readResourceFromRoot class.

      I wonder whether there is a workaround for this. IMHO, JMX monitoring should be as light as possible..