On Sat, 7 Jul 2001, Craig R. McClanahan wrote:
> Well yes, it's bad, but so will any other reaction. What choices are
> there in handling it?
>
> (1) Current behavior of closing the connection and go back to
> accepting new connections (causes a client-side protocol error)
>
> (2) Pause and try again in a bit (but in the mean time, this
> thread cannot accept any new connections, so they stack up
> inside the server socket up to acceptCount and then start
> getting refused)
>
> (3) Ignore the maxProcessors parameter and create a new processor (and
> its associated thread) anyway (can lead to denial of service attacks)
>
> Have you a suggestion on how we might deal with this more effectively?
shouldn't this event be logged? it would be nice if this happened too
frequently for a warning to be sent to the server's administrator.
- donald
