Hi all, I'm using JBoss 3.2.6 with the bundled Tomcat. I am using Apache with the AJP13 connection to Tomact. In situations where we have major traffic spikes, the rate at which requests come in can be faster than the rate at which they are fulfilled. In this situation, the jk thread pool currentThreadCount hits the maximum (currently we have it set to 425 threads) and requests begin to take a long time to complete as the queue quickly backs up.
Is there a way to put a maximum size limit on the number of requests to queue up? I think it's Tomcat which owns the queue. Ideally, I would have a 503 sent to any request over the queue limit (resource temporarily busy), rather than the user watching his browser spin for what can be minutes. I've seen an acceptCount configuration, but only when using HTTP connections, not for AJP13. Thanks. -Rob View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883245#3883245 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3883245 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user