On Oct 8, 2010, at 8:20 AM, Jaikiran Pai wrote:
By the way, as noted in that report, the JMX objects are still
lot of memory. I just quickly checked the jmx-console against AS trunk
and I see a lot of MBeans (mostly for debug level data) related to
classloader under the jboss.classloader domain:
... and more.
Those are created by the deployers on the Hornetq-integration integration. Those are
basically done by the dependency injection through those deployers. I'm not sure what
we could do about those here.