wicket0123 schrieb:
I want to check tomcat response time for requests when I run, say 500
concurrent users, on the server. I use the default setttings for tomcat
which means my maxThreads = 40.
I have read from some articles suggesting to use JMX Console to monitor
tomcat. But, then i read from other articles that JMX adds overhead to the
server. Basically, I am looking for a way to monitor tomcat performance
under load w/o affecting server performance by running the tools.
Now, i read from an article to use Valves to log the metrics into a log file
and process that later. My question is: is that the best way to go w/o
purchasing any commercial software?
Builtin possibilities (not exactly what you want, but a starting point,
especially if your observed values in JMeter are far away from your target):
- Add %D to the pattern in the access log valve (%D=millisecond response
time)
- Look at the MBeans. Overhead for monitoring purposes is not a problem,
as long as you don't try to get all MBeans like once a second or more
often. Overhead relative to CPU needed for processing will be low
especialy compared to doing stress tests with 100 or more requests per
second.
Examples for MBeans:
- each Servlet has one, showing accumulated number of calls to the
servlet, accumulated processing time, as well as min and max
- each ThreadPool has one, showing number of threads and busy threads
Get yourself a complete list, e.g. via
http://myserver/manager/jmxproxy?qry=*:*
and take an hour or two to go through them.
JConsole looks nicer to simply view values, but if you want to keep the
results, parse the results etc. jmxproxy is a better start.
Regards,
Rainer
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
