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
Memory leak with failed JMX connections with JBoss EAP 7.2
Solution verified - Updated on
Request a new translation or translation update
A translation for your language preference does not exist. Click below to request a translation for your selected language.
Issue
Subscriber Exclusive Content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.