Great work - but I'm curious, wouldn't be better to explore the alternative direction - i.e. detect when the server is too loaded and send a quick 502 ?
Maybe with some extra logic - like serve existing sessions first, provide some notifications that can be used by a load balancer ( or pager :-) to up more servers, or some notification to be used to disable some expensive functionality ? In a real world situation - I would rather have the server not accept 20.000 connection and do all of them badly. It's in the same line with 'fairness' and handling slashdot-ing, but in a different way. Costin On 3/10/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
Remy Maucherat wrote: > Mladen Turk wrote: >> (backlog) > > For some reason, I have yet to see that backlog behave like it is > supposed to in Tomcat. > > As my proposed long[] array is (supposedly) the same thing as the OS > backlog, maybe Filip can experiment with the "backlog" attribute (by > default, it's only 100, but could be set to a large value, like 20000, > to see what it does in his test). yes, I'll do that indeed, it will be an interesting test. One it will test if they actually do get backlogged, the second one if the backlog will get serviced before it times out. Thanks everyone for the feedback, I'll let you know how everything progresses. Filip --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
