Does anyone happen to know what module this might be? -----Original Message----- From: Morgan Gangwere [mailto:0.fractalus@xxxxxxxxx] Sent: Saturday, July 08, 2006 11:18 PM To: users@xxxxxxxxxxxxxxxx; jwanderson@xxxxxxxxxxxxx Subject: Re: Q: How to "force" HTTP 503 when Apache hits MaxClients somewhere there is a module that will allow you to auto-redirect if a certain variable (in this case "clients" or "numberClients") reaches or exeeds a certain value (in this case, 191, 1 over the max, so that when user number 191attempts connection, it kicks him, but user 190 can freely use the app). this was what I did to eliminate the long-wait time on subeta.org: it shows that if the server load is 1% or more over the max (200%, because its OK, but the apache distribution is built from pure, altered, mangled source.) On 7/8/06, James W. Anderson <jwanderson@xxxxxxxxxxxxx> wrote: > I have an application front-ended by Apache 1.3, and the application cannot > handle more than roughly 200 concurrent requests. We throttled back Apache > by > setting MaxClients to 190 and that seems to regulate the load and prevent > the > application server from crashing. The problem is, if the number of requests > to > Apache exceeds 190 Apache queues those additional requests and users end up > seeing very long response times. Instead of having our users watch the > hourglass we'd like Apache to immediately return "server too busy" responses > (HTTP 503?) as soon as it reaches MaxClients. How can we do this? > > > -- "Space does not reflect society, it expresses it." -- Castells, M., Space of Flows, Space of Places: Materials for a Theory of Urbanism in the Information Age, in The Cybercities Reader, S. Graham, Editor. 2004, Routledge: London. p. 82-93.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
|