Shapira, Yoav writes:
I think your testing, servlets, configuration is all fine. The
maxProcessors-1 observation is something I've noticed in the past, but
as you say I don't think many people care because they deal with ~75
maxProcessors (the default value).
Thanks - glad to know I'm not off
The second observation: two requests to the same servlet always
handled serially. Tomcat normally creates one instance of a servlet
for every declaration in web.xml. The exception is SingleThreadModel
(deprecated, don't use this) servlets. There's no provision in tomcat
to create more
V4.1.29 Coyote Connector / minProcessors maxProcessors
/
Confusion
The second observation: two requests to the same servlet always
handled serially. Tomcat normally creates one instance of a servlet
for every declaration in web.xml. The exception is SingleThreadModel
(deprecated, don't use
Hi,
This suggested to me that with minProcessors=1 and
maxProcessors=2, the server would allow 2 concurrent connections.
Yup.
Seems maximum_concurrent_connections=(maxProcessors - minProcessors),
a slightly different relationship than I gathered from the docs.
I was hoping someone could
Yoav,
Thanks for the quick reply...
Create a servlet that takes a long time to process, so you can easily
observe the connections. Then make sure you make two concurrent
requests to that servlet, and that the servlet's HTML output doesn't
contain images, CSS references, or any other entities
Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 25, 2004 1:56 PM
To: [EMAIL PROTECTED]
Subject: RE: TC V4.1.29 Coyote Connector / minProcessors maxProcessors
/
Confusion
Yoav,
Thanks for the quick reply...
Create a servlet that takes a long time to process, so
I'm a little confused regarding TC V4.1.29 Coyote HTTP/1.1 Connector
attributes minProcessors and maxProcessors. Server config docs state
minProcessors == number of connection threads to start initially
and maxProcessors == the maximum number of connection threads that
the server will create.
