> From: Christopher Schultz [mailto:ch...@christopherschultz.net] > Subject: Re: splitting thread pool > > The only way I know of to do this is with separate connectors:
One thing that hasn't been discussed is whether HTTP keep-alives are involved. If so, then using the NIO connector would free up threads that are otherwise doing nothing but waiting for more requests on the same connection to show up. (Disabling keep-alives would also do this, with an associated performance cost.) An alternative to using a filter, multiple connectors, or impacting performance with a front-end traffic cop is to use a set of ServletRequestListener classes that would keep track of the number of concurrent requests for the webapps of interest, and throttle accordingly. Since that would run in-process, it should give better performance and be less overhead than any kind of front-end director. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
