On 22/12/2009 12:55, Rainer Jung wrote:
On 22.12.2009 13:26, DOrlov wrote:
Rainer Jung-3 wrote:
You can add "%D" to the pattern for the omcat access log, which will
output the response time in milliseconds how Tomcat determined it.
Already done for most cases values are 0,1,2 ms
Max value which I ever find in the log ~ 20 ms
So then GC, locking and similar stuff is very unlikely, because by far
most of the code executed for rquest handling is included in this time
measurement. Sounds like either your java probing app has an issue, or
the network infrastucture?
Maybe you can sniff the network traffic on the probing client, wait
until it happens and look at the data stream for this point in time.
Data trafic between service and probing server should not be that high.
It may just be a temporarily slow route to the client. [shrug]
p
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
