No priorities. You can configure multiple connectors with different
thread counts and let your lb route on the correct connector based on
the URL.
Alec Swan schrieb:
Rainer,
we are not using Apache web server. Instead, HTTP requests get sent
directly
to the servlets in Tomcat. We do,
Hi all,
sorry for reposting. I posted the original message before I completed
registration, so I am not sure if got through.
I have two servlets: Worker and Status. Worker servlet gets hit very
frequently and consumes all available Tomcat threads (configured via
maxThreads). Thus, whenever I
You can configure two connectors with associated pools. If you need to
talk to both parts of the app under the same name and port, you can
front those two connectors (ports) with apache/mod_jk. With a sufficient
recent version of mod_jk you can configure several workers to forward to
different
Rainer,
we are not using Apache web server. Instead, HTTP requests get sent directly
to the servlets in Tomcat. We do, however use the (hardware) load balancer.
Is there a way to just configure Tomcat to allow some servlets have higher
priorities than others or dedicate a pool of connections to
Hi all,
I have two servlets: Worker and Status. Worker servlet gets hit very
frequently and consumes all available Tomcat threads (configured via
maxThreads). Thus, whenever I try to access the Status thread I have to wait
a long time. Is there a way to either dedicate some threads to Status
