• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Tomcat localAccess timing?

 
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
 
Don't touch me. And dont' touch this tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic