Memory leak with failed JMX connections with JBoss EAP 7.2

Solution Verified - Updated

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP) 7.2

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.

Resolution

Apply the JBoss EAP 7.2 CP03 containing the fix when available.

Root Cause

Content from issues.jboss.org is not included.JBEAP-16931 covers this issue.

SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.