DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7177 Apache/mod_jk/Tomcat Connectivity Problem ------- Additional Comments From [EMAIL PROTECTED] 2002-03-20 20:31 ------- this is a known problem with mod_jk/ajp13 where connections are permanent and created by webserver (iis/apache) depending the max numbers of threads/child allowed on webserver. You should really have more threads in tomcat 3.3/4.0 than possible threads/child in webserver. take a look at server.xml to set max threads in 3.3 : <Ajp13Connector port="8009" maxThreads="200" maxSpareThreads="50" minSpareThreads="10" /> or max processor in 4.0 <Connector className="org.apache.ajp.tomcat4.Ajp13Connector" port="8009" minProcessors="20" maxProcessors="200" acceptCount="10" debug="0"/> Also take care of jvm garbage collection which may introduce freeze in java side while the native part is still sending requests and create new ajp connections. read the excellent analysis From Glenn Nielsen... -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
