On 03 October 2006, Dan Adams said:
> Hmm, I don't think that is the culprit. I think all of our stuff is
> thread safe. We're using a framework (Tapestry) which shields us from
> threading issues like that and prevents us from storing request stuff in
> the session. Also, if that were the case wou
Hi -- we've recently had problems with Tomcat on one server getting
overloaded and then refusing further requests. What happens is that
more and more request-processing threads get stuck on some slow
operation (eg. database query, opening a socket to another server),
until eventually Tomcat's thre
On 04 May 2006, Ken Dombeck said:
> We have 2 applications installed inside the same Tomcat 5.0 instance
> app1 and app2. URL app1.url.com is for app1 and app2.url.com is for
> app2. Both URLs have the same ip address but still hit port 80. The
> maxThreads for the connector is set to 100.
>
> T
On 02 May 2006, Tim Funk said:
> An "easier solution" is to throttle the webapp via a filter. For example:
Good idea, thanks! I'll try to implement that and report back to the
list.
Greg
-
To unsubscribe, e-mail: [EMAIL
On 02 May 2006, Mike Scherer said:
> How and where do I specify the JAVA_HOME or the JRE_HOME Environment
> variables?
What OS are you using? With most Unix-like systems, you just do
something like
export JAVA_HOME=...
before running the Tomcat launch script. E.g. if you start Tomcat from
an
We've been using Tomcat 4.1.30 happily for a couple of years now, but
every so often one badly-behaved webapp can make life unhappy for
everyone living in the container. (Our Tomcat deployment is part of a
suite of applications that run on a small cluster of Linux servers; all
of the webapps runni
