> 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
On 15/11/2010 20:30, Luke Meyer wrote:
> 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:
> maxThreads="250" protocol="AJP/1.3" />
>
> See the typo? "connectionTimeOut" should be "connectionTimeout". Normall
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
