wood burning stoves 2.0*
The moose likes Tomcat and the fly likes Tomcat localAccess timing? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Products » Tomcat
Bookmark "Tomcat localAccess timing?" Watch "Tomcat localAccess timing?" New topic
Author

Tomcat localAccess timing?

Dan Hop
Greenhorn

Joined: Aug 02, 2010
Posts: 7
Hi all, I have a couple of questions in regards to how/when the access logs actually begin to 'see' a request.

In particular, lets say I have a server configured, as follows:
maxThreads=200
acceptCount=100

This configuration implies at most 300 connections can be established, my question is...

1) Will I see Requests in the access log, that never got enqueued (i.e. say the 301 concurrent connection request)..I would think not...
2) In the local Access log valve you can configure duration of request. (does this duration include the time in the 'queue', or is it only the time spent processing the actual request?
i.e. if the local Access log say the request took 30 seconds...does that mean the connection was held for about 30 seconds.or could it say actually have sat in the 'queue' for say 10 minutes..or what-ever..

thanks
Dan
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Tomcat localAccess timing?
 
Similar Threads
(WebLogic 8.1) Persist Messages Using JMS Queue
Websphere MDB MQ listener port problems
getLocalPort()
Servlet handling multiple requests from applet
Transactions - JTA or JDBC?