Thanks for the idea Peter. I thought of maybe putting a filter on the certain url pattern that I want, but instead of turning back the user, I could put his thread to sleep for aset amount of time and have him try again. Hopefully by then some of the earlier threads will have finished and he can be let through.
Do you some inherent problem with this? Thanks, Adam. Peter Crowther wrote: > >> From: adamle [mailto:[EMAIL PROTECTED] >> I am looking for a solution that for a certain url pattern >> only allows a >> certain number of requests to be serviced at the same time. >> This would >> solve my problem, while not affecting servicing lighter pages. > > Makes sense. > > If you can stand for your users to get a 'Busy, please try again later' > message, then one approach would be to put a Filter in front of the > relevant pages. Whenever it sends a request for processing, it > increments a filter-wide counter; whenever a request returns from > processing, it decrements the counter; if the counter is above a certain > value when the request comes in, don't forward the request and show the > client a try-later message. > > If this isn't appropriate, I'm out of ideas - but I'm a lightweight on > this forum, and have never used AJP. I suspect some of the better minds > on here will weigh in later! > > - Peter > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Limit-Num-Requests-tf2858769.html#a7987715 Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
