[jira] Updated: (SOLR-1843) JMX name collision when running multiple SOLR instances/webapps in the same ServletContainer

["Constantijn Visinescu (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Constantijn Visinescu updated SOLR-1843:
----------------------------------------

    Attachment: SolrConfig.java
                JmxMonitoredMap.java

Based on revision 829938 : Starting Solr 1.4 branch.

> JMX name collision when running multiple SOLR instances/webapps in the same ServletContainer
> --------------------------------------------------------------------------------------------
>
>                 Key: SOLR-1843
>                 URL: https://issues.apache.org/jira/browse/SOLR-1843
>             Project: Solr
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 1.4
>         Environment: Resin 3.1.6, possibly other application containers
>            Reporter: Constantijn Visinescu
>            Priority: Minor
>         Attachments: JmxMonitoredMap.java, SolrConfig.java
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> http://www.mail-archive.com/solr-user@lucene.apache.org/msg33921.html
> When i run multiple independent SOLR webapps both with JMX enabled there seems to be some sort of collision when registering Mbeans causing my application server to throw exceptions for each mbean it tries to register for all applications after the first.
> This seems to be due to collision issue of sorts with both applications trying to register their mbeans under the name "solr"
> This patch fixes the issue by allowing the user to specify the name under which MBeans are registered in solrconfig.xml like so:
>   <jmx rootName="mySolr" /> 
> i went with rootName since in the code the variable is called jmxRootName.
> Constantijn Visinescu

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.