[
https://issues.apache.org/jira/browse/SOLR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-256:
--------------------------
Attachment: jmx.patch
Sharad: my concern with your most recent patch is that if a servlet container
uses it's own config to drive programmatic JMX Server creation (jetty plus
appears to do this past on the example jetty-jmx.xml config file, but i haven't
actually confirmed this), then Solr won't detect it because it's looking
explicitly for the system properties.
based on the javadocs your findMBeanServer(null) idea seems right on the money
... i'm attaching a tweak to your patch that uses this appraoch, and it seems
to work great, what do you think?
(was there a reason you decided to look for the properties explicitly instead
of try this appraoch?)
Any JMX experts want to chime in whether we should be doing something
differently?
> Stats via JMX
> -------------
>
> Key: SOLR-256
> URL: https://issues.apache.org/jira/browse/SOLR-256
> Project: Solr
> Issue Type: New Feature
> Components: search, update
> Reporter: Sharad Agarwal
> Priority: Minor
> Attachments: jmx.patch, jmx.patch, jmx.patch, jmx.patch, jmx.patch
>
>
> This patch adds JMX capability to get statistics from all the SolrInfoMBean.
> The implementation is done such a way to minimize code changes.
> In SolrInfoRegistry, I have overloaded Map's put and remove methods to
> register and unregister SolrInfoMBean in MBeanServer.
> Later on, I am planning to use register and unregister methods in
> SolrInfoRegistry and removing getRegistry() method (Hiding the map instance
> to other classes)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
