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
connection reuse.
- Original Message -
From: "Luke Meyer"
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
> The BIO connector doesn't complain due to how properties are handled
> internally. The NIO and APR/native connector will log warnings.
OK, good to know. I noticed the default HTTP connector also doesn't warn about
bogus properties. Hadn't checked the rest.
> AJP connections are intended to pe
Tomcat 6.0.29, HotSpot 1.6.0_21 on CentOS 5.
I had a problem recently where someone configured a standard AJP connector like
this:
See the typo? "connectionTimeOut" should be "connectionTimeout". Normally
Tomcat complains when you have bogus properties, e.g.:
WARNING org.apache.tomcat.util.di
