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

["Jean-Baptiste Onofré (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KARAF-6114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071933#comment-17071933 ] 

Jean-Baptiste Onofré commented on KARAF-6114:
---------------------------------------------

Wrapping the required artifact as a bundle which is a fragment with JMX collector as host just works fine.

> 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é
>            Priority: Major
>             Fix For: decanter-2.3.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
(v8.3.4#803005)