tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: Handling requests when under load - ACCEPT and RST vs non-ACCEPT
Date Fri, 02 Nov 2012 20:30:37 GMT
Hash: SHA1


On 11/2/12 3:51 PM, Mark Thomas wrote:
> On 02/11/2012 19:13, Asankha C. Perera wrote:
>> Hi Esmond
>> You are correct. As I recently found out Tomcat and Java is not
>> causing this explicitly, as I first thought. So there is no 'bug'
>> to be fixed.
>> But I believe there is an elegant way to refuse further
>> connections when under load by turning off just the 'accepting'
>> of new connections, and causing the client to see a 'connection
>> refused' instead of allowing new connections, accepting requests
>> and then resetting connections with a 'connection reset',
>> preventing the client from a clean failover for non-idempotent
>> requests. Apache HttpComponents/NIO library already supports
>> this, so its something that Tomcat too can support if the 
>> community thinks it would be useful.
> Or you could just read the configuration documentation for the 
> connector. Hint: acceptCount - and it has been there since at
> least Tomcat 4.

That's kind of what I was thinking, but getting information from the
OP was like pulling teeth. I just gave up.

Note that his configuration *does* include an acceptCount which is
being changed from "1" to "1000". I think the problem is that the OS
might be a little fuzzy with that value.

If HttpComponents works as the OP expects, I wonder if he'd be willing
to give us the configuration he uses for *that*? Perhaps there is some
kind of TCP option that HttpComponents is using that Tomcat does not.

- -chris
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools -
Comment: Using GnuPG with Mozilla -


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message