Hi. We use JavaMelody for "moment performance checks" on test box and Zabbix monitoring system to have whole history. Zabbix can use JMX connection to Tomcat instance and have set of included teamplates, for example - number of threads, current memory usage, gzip usage and so on. Main virtue of Zabbix ++ JMX is that it store all data in database + can draw graphs.
2014-04-08 18:00 GMT+03:00 Jeffrey Janner <jeffrey.jan...@polydyne.com>: > > -----Original Message----- > > From: Randhir Singh [mailto:randhir.si...@sterlite.com] > > Sent: Tuesday, April 08, 2014 6:05 AM > > To: users@tomcat.apache.org > > Subject: How to monitor performance of tomcat > > > > We have an application which has JBoss as the application server with > > Tomcat as the web server, our application has Oracle 11g as the > > database. I would give some further background to the issue we are > > facing, since the last 1 1/2 months, the application slows down. > > Sometimes it comes back to normal, specially on week-ends. But other > > times we restart JBoss & Tomcat to bring back the application to > > normal. > > > > > > > > We have been using jconsole to monitor tomcat like > > > > > > > > jconsole 10.101.17.79:8891 > > > > > > > > which monitors our tomcat for a work order system. If the memory usage > > does not show spike and shows constant reading, the GC button is > > clicked to invoke the garbage collector. > > > > > > > > I checked out on the net and got some clue as below: > > > > > > > > 1) Javamelody - It seems to be a 3rd party tool which is not > > recommended. > > > > 2) There is a command mentioned to see the admin console, > > http://<IP:port>/ but it is not displaying the required page. > > > > > > > > Please give your inputs whether jconsole should be a help in the right > > direction or some other way to monitor the performance of Tomcat. > > > Jconsole and JVisualVm are quite useful tools for basic monitoring, if you > understand how to use them and their limitations. > Why did you get the impression that JavaMelody is not recommended? It > does offer an awful lot of monitoring/debugging information, but you need > to careful in setting it up. Under Tomcat 7, it will autodeploy with no > security by default and expose a lot of potentially confidential > information to whomever connects using the well-known "context" for it > (which can't be changed). If you want to use it, I suggest limiting it to > your development environment only, or reading up on how to secure it as > best as possible. > Jeff > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
