> You allowed infinite connections, but there are other resources, such as
> threads, that you did not change.  It appears that your threadpool was
> exhausted.
>
>       --- Noel
>

I suspected that, in fact i should (and will) limit back such number of
connections.

My point is: was it some kind of attack? Was it a denial-of-service attack?
In the latter case, to avoid service disruption, would it be better to
increase or decrease the connections/threads etc?

More generally, has anyone in the James comunity been thinking about the
problem of being attacked by a very high number of requests? Or even has
been attacked?
Perhaps there could exist some auto-protection inside James, for example not
allowing more than a certain number of *open* connections/allocated threads,
or more than a certain number of connections/allocated threads
*per-unit-of-time* to the same IP.

Vincenzo


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to