Re: mod_jk connection issues, more information.

2002-12-18 Thread Simon Chatfield
The connectionTimeout was the solution, increasing the value of the other attributes simply delayed the problem. I had been using the Ajp13Connector earlier, then noticed this new attribute on they CoyoteConnector so tried that as a work around. So far so good in my testing. -Simon Milt Epst

Re: mod_jk connection issues, more information.

2002-12-18 Thread Milt Epstein
On Wed, 18 Dec 2002, Simon Chatfield wrote: > I made the following change > > port="8009" minProcessors="5" maxProcessors="100" > enableLookups="true" redirectPort="8443" > acceptCount="100" debug="0" connectionTimeout="2" > useU

Re: mod_jk connection issues, more information.

2002-12-18 Thread Simon Chatfield
I made the following change port="8009" minProcessors="5" maxProcessors="100" enableLookups="true" redirectPort="8443" acceptCount="100" debug="0" connectionTimeout="2" useURIValidationHack="false" protocolHandlerClassName="org.apa

Re: mod_jk connection issues, more information.

2002-12-18 Thread Milt Epstein
On Wed, 18 Dec 2002, Simon Chatfield wrote: > The number of open connections > > # netstat -a |grep 8009 |wc -l > 175 > # > > actually, I think that shows both sides of the connection between apache > and tomcat + the listener, so that's 87 connections... [ ... ] I think how many of the

mod_jk connection issues, more information.

2002-12-18 Thread Simon Chatfield
The number of open connections # netstat -a |grep 8009 |wc -l 175 # actually, I think that shows both sides of the connection between apache and tomcat + the listener, so that's 87 connections... Now streaming in the apache errors_log er [Wed Dec 18 11:50:48 2002] [warn] (128)Networ