-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/04/2012 16:20, Christopher Schultz wrote:
> On 4/12/12 4:37 AM, Mark Thomas wrote:
>> In short, disabling mod_jk keep-alive frequently has no
>> noticeable performance impact (some customers of mine reported a
>> performance improvement!)
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 4/12/12 4:37 AM, Mark Thomas wrote:
> HTTP keep-alive is nearly always between a client and a server
> across the internet. mod_jk keep-alive is nearly always between a
> client and a server on the same LAN and often on the same machine.
>
Christopher Schultz wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Luke,
>
>On 4/11/12 5:17 PM, Luke Meyer wrote:
>> Just noticed what I was missing about connectionTimeout - it's the
>> default for keepAliveTimeout. So, that clears that up.
>>
>> Still don't think it's a "huge neg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luke,
On 4/11/12 5:17 PM, Luke Meyer wrote:
> Just noticed what I was missing about connectionTimeout - it's the
> default for keepAliveTimeout. So, that clears that up.
>
> Still don't think it's a "huge negative performance impact!" to
> disable
;
To: users@tomcat.apache.org
Sent: Tuesday, April 10, 2012 5:09:17 PM
Subject: mod_jk - Firewall connection dropping
I have some questions about the documentation at
http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html regarding
the Firewall Connection Dropping section. I don
I have some questions about the documentation at
http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html regarding
the Firewall Connection Dropping section. I don't think it's quite right, but
maybe I misunderstand.
To quote the sections in question:
" Many firewalls will allow
