On 13/01/2011 23:05, Alec Swan wrote: > Hello, > > Our webapp gets periodically hammered by our client applications causing > Tomcat to run out of threads. This prevents us from being able to use Tomcat > Manager and check the server status. > > Is there a way to assign a dedicated thread to Tomcat Manager so that it > will never be used to process any other client requests?
The short answer is no. The longer answer is take a look at the SemaphoreValve. You should be able to subclass that and override controlConcurrency. Something along the lines of limit all users from non-admin IPs to 390 concurrent requests and have 400 threads on the connector. Just be aware I'm not sure how widely used (and hence tested) that valve is. On the other hand Remy wrote it so the chances of it failing are pretty slim. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
