This is related with support ticket 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:
Instead of getting that URI, ONMS gives us a URI of
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
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.