Remy Maucherat wrote: > Hi, > > I proposed that to Costin a few days ago, but got not so enthusiastic > comments. > The idea would be to add a new monitor servlet to the manager webapp. It > would generate data similar to http://www.apache.org/server-status. It > would mostly (exclusively ?) use JMX to retrieve the components > statistics.
I'm not so enthusiastic for few reasons. We still have a lot of work to do in our core area - and it seems the ammount of time most people have is limited. +1 on extending the manager servlet to also display monitoring data, and to use the new JMX model - if 5.0 will use recommend using JMX to control tomcat, the manager should be an example of that instead of using the internal APIs. /manager is also close to /server-status ( or /jkstatus ). There are 3 JMX consoles available ( each JMX impl. has one ). A generic console would be nice - but it doesn't belong to tomcat ( maybe in commons). > That's not a high priority task for me, but something I'd like to get > done eventually, and I'm looking for some feedback. I understand that > there are existing agents for JMX that can be used to provide more > powerful remote access to the statistics (HTTP, RMI, etc), but these > tools do not have the ability to give a user a quick and comprehensive > look at the Tomcat status (although they allow much more complex > operations, and it's not my objective to replace them). For remote statistics - I added a small experimental remote-JMX mechansim for mod_jk ( which obviously can't support direct JMX ), and I plan to extend it and merge it in modeler. IMO any generic JMX effort should be in commons ( modeler or a different component ). Costin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
