[jboss-jira] [JBoss JIRA] Updated: (JGRP-504) Support direct injection of MBeanServer into JChannelFactory

[Bela Ban (JIRA)]

     [ http://jira.jboss.com/jira/browse/JGRP-504?page=all ]

Bela Ban updated JGRP-504:
--------------------------

    Fix Version/s: 2.6

> Support direct injection of MBeanServer into JChannelFactory
> ------------------------------------------------------------
>
>                 Key: JGRP-504
>                 URL: http://jira.jboss.com/jira/browse/JGRP-504
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>            Priority: Minor
>             Fix For: 2.6
>
>
> Currently org.jgroups.JChannelFactory finds the MBeanServer it should use via a "discovery" algorithm that will:
> 1) Use the server registered as "jboss" if one exists
> 2) Else use the first mbean server found, which will be the platform mbean server in a JDK env.
> This will break if the target mbean server isn't the platform mbean server and isn't named "jboss".
> I don't see any reason org.jgroups.JChannelFactory can't expose a setter for this.  The usage for this would be:
> The org.jgroups.jmx.JChannelFactory class should implement javax.management.MBeanRegistration.  This is the object that external code (e.g. microcontainer or AS 4.x ServiceController, or custom user code) initially registers in JMX. Via the MBeanRegistration.preRegister(MBeanServer server, ObjectName name) callback the org.jgroups.jmx.JChannelFactory is made aware of exactly what mbean server is being used.  The org.jgroups.jmx.JChannelFactory then passes this into the org.jgroups.JChannelFactory via the setter.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira