Can't monitor JBoss EAP 6.1.0 or later with the JMXMonitor/JMXCollector because they don't support jmx-remoting protocol

Description

This is related with support ticket 2735:
https://mynms.opennms.com/Ticket/Display.html?id=2735

Here is a brief description about the problem and the proposed solution based on customer's input:

We think we may have a fix for the problems we have been having with JSR160Collector on JBoss EAP 6.1.0 or later.

Here is the gig: when you try to connect to it using a method (using current code) that jeffg gave us to TRY to connect to a JBoss EAP 6.1.0 server:

service:jmx:remoting-jmx://IP_ADDRESS_HERE:9999/

Instead of getting that URI, ONMS gives us a URI of

service:jmx:remoting-jmx:///jndi/remoting-jmx://IP_ADDRESS_HERE:9999/

The IP is correct but the extra '/jndi/' is excess content that is causing the connection to fail.

The following code in org.opennms.protocols.jmx.connectors.JMXSecureConnectionFactory.java needs to be changed from

To

The customer tried the solution on their environment for several kind of JMX servers besides recent versions of JBoss, and everything is working as expected.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Alejandro Galue September 25, 2014 at 10:38 AM

Indeed the patch will be part of the next build thanks to you

Charles Hopkins September 25, 2014 at 10:36 AM

It works. I just was trying to help make sure it gets into the next builds.

Alejandro Galue September 24, 2014 at 3:11 PM

I'm not sure what is missing, I've committed the changes into 1.12 branch (which is merged into 1.14 automatically) after you told me it works. I mean, the change has been applied into both JMX connection factories.

Charles Hopkins September 24, 2014 at 3:08 PM

Alejandro, remember to add the most recent patches to this.

Our ticket was:
https://mynms.opennms.com/Ticket/Display.html?id=3257

The other relevant / related bug was: http://issues.opennms.org/browse/NMS-6830

Alejandro Galue June 9, 2014 at 6:18 PM

Fixed on revision f286362d63f8109f4ff770cc7a0f7de9445ec303 for 1.12.

This will be merged into master automatically.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created June 9, 2014 at 6:16 PM
Updated January 27, 2017 at 4:20 PM
Resolved June 9, 2014 at 6:18 PM