Yoav,
Thanks for the + feedback. Apologies for response delay - I'm digest only
and also had wicked work backlog past couple weeks. Will submit a Bugzillia
item as requested.
Additional questions seem relevant prior to that (in the "be careful what
you ask for..." department ;-). With the ou
I have several questions that apparently center around the
org.apache.tomcat.util.threads.ThreadPool class contained in the
tomcat-util.jar file included in the Tomcat V4.1.30 distribution.
Background:
Using V4.1.30 in a standalone, relatively minimal configuration with the
Coyote HTTP/1.1 C
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 instanc
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 in
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 w
y, no web pages, JSP,
etc. Limiting concurrent connection count to relatively low numbers
due to resource constraints on many of these platforms.
Any feedback would be greatly appreciated.
Regards,
jblayer
-
To unsubscribe, e-mai
