[jboss-jira] [JBoss JIRA] (JGRP-2394) Provide an overloaded JmxConfigurator.registerChannel that takes an ObjectName to be used as prefix instead of the domain

[Nistor Adrian (Jira)]

     [ https://issues.jboss.org/browse/JGRP-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nistor Adrian updated JGRP-2394:
--------------------------------
    Description: 
The JmxConfigurator.registerChannel variant that takes a domain is not enough for use cases where multiple apps running in a jvm join the same JGroups cluster and also share the same jmx domain. In this case the channel MBean object names will collide. The de-duplication mechanism using random number suffixes does not provide predictable results.  Avoiding jmx domain sharing is also not possible due to the nature of the use case.

So we propose adding someting like this:
JmxConfigurator.registerChannel(JChannel channel, MBeanServer server, ObjectName namePrefix,  String cluster_name, boolean register_protocols)

which would allow the application using JGroups to have greater control of the generated object names for channel and protocols.  The namePrefix will provide the domain and also a key-value list that will serve as the prefix for all ObjectNames internally generated by JGroups. It will be the caller's task to ensure this leads to generation of unique names.

  was:
The JmxConfigurator.registerChannel variant that takes a domain is not enough for use cases where multiple apps running in a jvm join the same JGroups cluster and also share the same jmx domain. In this case the channel MBean object names will collide. The de-duplication mechanism using random number suffixes does not provide predictable results.  Avoiding jmx domain sharing is also not possible due to the nature of the use case.

So we propose adding someting like this:
JmxConfigurator.registerChannel(JChannel channel, MBeanServer server, ObjectName namePrefix,  String cluster_name, boolean register_protocols)

which would allow the application using JGroups to have greater control of the generated object names for channel and protocols.  The namePrefix will provide the domain and also a key-value list that will serve as the prefix for all ObjectNames internally generated by JGroups. It will be the callers task to ensure this leads to generation of unique names.



> Provide an overloaded JmxConfigurator.registerChannel that takes an ObjectName to be used as prefix instead of the domain
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JGRP-2394
>                 URL: https://issues.jboss.org/browse/JGRP-2394
>             Project: JGroups
>          Issue Type: Enhancement
>    Affects Versions: 4.1.6
>            Reporter: Nistor Adrian
>            Assignee: Bela Ban
>            Priority: Major
>
> The JmxConfigurator.registerChannel variant that takes a domain is not enough for use cases where multiple apps running in a jvm join the same JGroups cluster and also share the same jmx domain. In this case the channel MBean object names will collide. The de-duplication mechanism using random number suffixes does not provide predictable results.  Avoiding jmx domain sharing is also not possible due to the nature of the use case.
> So we propose adding someting like this:
> JmxConfigurator.registerChannel(JChannel channel, MBeanServer server, ObjectName namePrefix,  String cluster_name, boolean register_protocols)
> which would allow the application using JGroups to have greater control of the generated object names for channel and protocols.  The namePrefix will provide the domain and also a key-value list that will serve as the prefix for all ObjectNames internally generated by JGroups. It will be the caller's task to ensure this leads to generation of unique names.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)