[logback-dev] [JIRA] Updated: (LBGENERAL-28) JMX configurator should be able to use MBeanServers with a domain name

[cj91 (JIRA)]

     [ http://jira.qos.ch/browse/LBGENERAL-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

cj91 updated LBGENERAL-28:
--------------------------

    Attachment: JMXConfiguratorAction.java

sorry I can't submit a 'patch'... I don't have a GIT client and cannot install one. However, the change to specify an agent ID is quite simple, so I pulled the file from the maven source jar and made the necessary changes (less than 10 LOC).

Suggestions for further improvement would be to specify:

factoryClass="com.yourcompany.jmx.MBServerlocator"
factoryMethod="locateMBeanServer"

which would reflect on the specified class and invoke the method to return the server.

Enjoy!

> JMX configurator should be able to use MBeanServers with a domain name
> ----------------------------------------------------------------------
>
>                 Key: LBGENERAL-28
>                 URL: http://jira.qos.ch/browse/LBGENERAL-28
>             Project: logback-general
>          Issue Type: New Feature
>    Affects Versions: 0.9.16
>            Reporter: Celal Ziftci
>            Assignee: Ceki Gulcu
>         Attachments: JMXConfiguratorAction.java
>
>
> Currently, logback exposes an MBean to provide logging related controls via the inclusion of the following configuration:
> <jmxConfigurator /> 
> However, this *always* uses the platform mbean server:
> MBeanServer mbs = ManagementFactory.getPlatformMBeanServer();
> (can be found in class JMXConfiguratorAction, line# 54).
> I think it should be able to provide an option to use an MBeanServer with a specific domain, which is provided in the JMX spec.
> The code needs to use the following:
> List servers = MBeanServerFactory.findMBeanServer(agentId);
> and then use the first one, possibly giving a warning if there are multiple.
> This is crucial for our use-case, especially because we have separate MBeanServers in our web-app environment, and we need each application to use its own MBeanServer with a specific domain.
> So, all in all, can we add an attribute of some sort, so that we can do the following:
> <jmxConfigurator agentid="someMbeanServerId"/> 
> and if this is set, the code uses:
> MBeanServer mbs = MBeanServerFactory.findMBeanServer(agentId).get(0);
> and otherwise, it does whatever it used to do.

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