[
https://issues.apache.org/jira/browse/SOLR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507660
]
Hoss Man commented on SOLR-256:
-------------------------------
Sharad: JMX is one of those things i don't really understand very well, but i
tried out the patch and played around with jconsole and it's really cool.
one thing i'm not clear on (forgive my jmx ignorance) when trying to figure out
how jconsole worked, i found some info saying that to enable JMX in a java app,
you use "-Dcom.sun.management.jmxremote" option on the java command line ...
doing that even without this patch allowed jconsole to "autodetect" that the
"start.jar" process on my local machine supported JMX and gave me some
interesting stats on things like memory and thread usage info from the jetty
instance (including MBeans for the java.util.Logger's SOlr creates).
With the patch, it doesn't seem to matter wether i use that commandline option
or not i can only get access to the new solr specific stats if i tell jconsole
to explicitly connect to the service:jmx:... url that shows up in the log. but
in this case it can't get access to the other interesting stats from before
(memory, thread, etc...) ... it seems like i can make two seperates "sessions"
(forgive me if my terminology is wrong) to get this info, but not in the same
session
Is there a way to "register" the SOlr MBeans with the JVMs main JMX instance so
all of hte info is available together?
also: if we're going to have options for specifying the port for remove JMX
connections, shoudl we also have options for the user/pass to connect with?
> 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
>
>
> 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.
