You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2019/01/26 07:09:00 UTC

[jira] [Created] (KARAF-6114) Support custom JMX protocol in JMX collector

Jean-Baptiste Onofré created KARAF-6114:
-------------------------------------------

             Summary: Support custom JMX protocol in JMX collector
                 Key: KARAF-6114
                 URL: https://issues.apache.org/jira/browse/KARAF-6114
             Project: Karaf
          Issue Type: Improvement
          Components: decanter
            Reporter: Jean-Baptiste Onofré
            Assignee: Jean-Baptiste Onofré
             Fix For: decanter-2.2.0


Some middlewares (like wildfly) uses a custom/specific JMX protocol.

For instance, wildfly uses the following JMX URL:

{code}
service:jmx:http-remoting-jmx://localhost:9990
{code}

The {{http-remoting-jmx}} protocol requires the {{jboss-client.jar}}, loading by the Decanter JMX Collector. This could be achieve by importing the package (dynamic or optional) and using {{JMXConnectorFactory.PROTOCOL_PROVIDER_CLASS_LOADER}} to define where it's located.

I'm improving the JMX collector to be able to populate cleanly the classloader.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)