Anthony, On 3/30/16 6:08 PM, Anthony Biacco wrote: > On Wed, Mar 30, 2016 at 9:13 AM, Christopher Schultz < > ch...@christopherschultz.net> wrote: > > Edwin, > > > For my money, I wouldn't enable JMX because, for monitoring, JMX is a > heavy-handed protocol: you either have to maintain a persistent > connection to the server or you need to launch a whole JVM and connect > over JMX to get e.g. a single sample value (such as current throughput). > > I would recommend enabling the JMXProxyServlet through the manager > application, and then locking-down the manager application so you can > only access it from localhost. Also use a non-trivial password for > HTTP authentication for the manager. > > >> +1 >> i was using the jmxquery jar pulled from nagios and was slooow compared to >> the manager's jmxproxy (as would be expected). >> i just used the the perl script from >> https://wiki.apache.org/tomcat/FAQ/Monitoring and assigned a user to the >> manager-jmx security role in tomcat.
Nice to see someone else is using it ;) Feel free to contribute to it or just complain about anything you need. I'd like for that tool to be widely-useful. I use it a lot at $work, but it should be universally useful. -chris --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
