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
An "easier solution" is to throttle the webapp via a filter. For example:
Filter{
final int maxThreadCount=10;
int threadCount=0;
doFilter() {
synchronized(this) {
if (threadCount>maxThreadCount) {
response.sendError(SC_SERVICE_UNAVAILABLE);
return;
}
t
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
