JMX monitoring is memory inefficient

Solution Verified - Updated -

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 of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.