Memory leak with failed JMX connections with JBoss EAP 7.2

Solution Verified - Updated -

Issue

Monitoring software connects to JBoss via jmx using the jmx:remote+http protocol. The jboss-cli-client.jar from JBoss EAP 7.2 distribution was included in the monitoring client's classpath. Requests to JBoss servers that do not exist causes frequent "normal" refused JMX connections, but it leaks memory with each failure. Over time, monitoring client fails with OutOfMemoryError.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP) 7.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content