Howdy,
You might also use two tomcat instances -- much easier to tune.
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Parris, Edward G [mailto:[EMAIL PROTECTED]
Sent: Monday, February 02, 2004 5:38 PM
To: [EMAIL PROTECTED]
Subject: WHY? Tomcat 5 maxThreads too low
I have a single server running Tomcat supporting several webapps. The web apps fall
into two categories:
webapps that require quick response but that use few system resources
webapps that are expected to process for a long period and consume large amounts of
system resources
The goal is to
I have a single server running Tomcat supporting several webapps. The web apps fall
into two categories:
webapps that require quick response but that use few system resources
webapps that are expected to process for a long period and consume large amounts of
system resources
The goal is to
On Mon, February 2, 2004 at 2:38 pm, Parris, Edward G wrote:
I tried a similar configuration on Tomcat 5.0.18 but noticed a ThreadPool
warning on startup stating that my maxThreads setting was too low and that
it would be reset to 10.
WARNING: maxThreads setting (3) too low, set to 10
Does
David Rees wrote:
1. Recompile Tomcat 5, lowering the hard-coded minimum.
2. Implement a filter or some other type of synchronization in your
servlet which keeps track of the number of currently executing requests
and redirects the user to a different page with a meta refresh letting
them know
On Mon, February 2, 2004 at 6:28 pm, Josh Rehman wrote:
This brings up an interesting point. I'm too lazy to test it, but what
happens if you tomcat needs more threads than it is allowed? Does the
user get a 404?
No. If the acceptCount is set to more than 0, the request will sit in the
