Peter Buning wrote:
Hello,
we tested our tomcat 5.5 server (Debian system) with the apache
benchmark tool. We send requests for a small png-file (300 bytes).
Nearly all requests were done in 0 or 1 milliseconds. But there were a
few request which needed more than 10 ms and the slowest request needed
106 ms.
the 106 ms is logged in the access log file. We used the %D pattern for
the request time in millis.
It seems not to be a network problem. We can see the same behavior with
a remote and a localhost test. Nevertheless, does anybody know, when
tomact exactly starts and stop the time for logging the request?
We did A similar test with the YourKit Java Profiler, but can't find a
reason for the slow requests, too. The time for "all threads" and for
"java.lang.Thread.run" was less than the time for the longest request.
The Garbage Collector was not active while testing.
So, we want to know, why there are a few request that took so much more
time than the rest of the requests. Has anybody an idea where the time
can be consumed?
Are the requests from the benchmark tool made with "keep-alive" ?
What is the keepAlive setting for the Tomcat Connector processing these
requests ?
Depending on your configuration and how requests are being made, if keepAlive is set to a
high value, you may just have many Tomcat threads waiting for a follow-up request (*) on
each connection, before closing the connection and becoming available again to process
more requests.
(*) which may never come..
In your next message, paste the contents of your Tomcat's server.xml file, all comments
and private data removed.
Also tell how the requests are being issued (how fast, how many, with/without keepalive,
etc..)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
