On 22/05/2013 23:13, Vanga Palli, Ravindra Kumar wrote: > The timer starts when the incoming socket is assigned to a thread. So, what > you see in logs is a processing time but not queuing time.
Not quite. The timer starts once the request line has been processed Mark > > Thanks, > Ravi > > From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com] > Sent: Wednesday, May 22, 2013 2:32 PM > To: 'Tomcat Users List' > Subject: Need AccessLogValve results clarification > > I'm sure this was recently asked, but I couldn't find the thread. > I'm using the AccessLogValve with "%D" at the end of the string to get a > rough processing time per request. > I'm using straight connector threads, no executor pool. > The question is, when does the timer start for a request that ends up waiting > for a connector thread to process? > When the execution start, or when it gets put on the wait queue? > Ex: MaxThreads=50, AcceptCount=100, so assuming all 50 threads are busy, > does the timer start for request 51 when it is received or when it starts > processing. > > If it really matters, Tomcat 6.0.36, Java 6.0.43 (?) and Windows 2008 R2. > > Jeffrey Janner > Sr. Network Administrator > jeffrey.jan...@polydyne.com<mailto:first.l...@polydyne.com> > PolyDyne Software Inc. > Main: 512.343.9100 > Direct: 512.583.8930 > > [cid:image002.png@01CC0FB7.4FF43CE0] > > Speed, Intelligence & Savings in Sourcing > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
