Hi - I inquired about this some time ago, and learned a lot on the subject of JMX and Tomcat (and solr, too!), but never did find a definite answer. It doesn't look like anything JMX has been discussed on the list for some time, either.
I've been toying around with JMX lately in Tomcat, and think its really neat how I can use JMX to query Solr instances with it. I can see the number of searches, min/max docs, warmup time, indice sizes, all kinds of neat stuff. In our setup, we run several instances of Solr under one instance of Tomcat. I simply rename the WAR to soemthing we use internally - solr-people, solr-connections, solr-companies, etc etc. This part works fine and lets us have, use, and maintain invidual instances. On the subject of JMX, however, I find that Solr always reports to the /solr mbean, regardless of the Solr instance name. Although this was not completely unexpected behavior, I had hoped that the mbean that solr would interact with was also named by the same name that the invidual instance of Solr was named. What I'm finding is every instance reporting to /solr, which skews my queries. Although I can somewhat predict which searcher is which, its not reliable enough to be able to associate statistics with our named versions of our indices. So in summary, I'm trying to figure out how to rename the mbean that Solr uses, specifically for JMX, to something a bit more predictable and isolated. Anyone know if/how I can do this? Thanks! -dant
