It looks like you are seeing the same problem as some of the rest of us. It seems apache, tomcat or mod_jk does not close the connection after serving a request and the number of threads just keep building up. It seems to be a problem mainly on Redhat 8.
Have a look at the 'Problems with tomcat 4.0.1 and 4.1.18' message thread on http://www.mail-archive.com/[EMAIL PROTECTED]/thrd2.html and 'tomcat 4.1.18, apache 2.0.43, mod_jk 2.0.43' message thread http://www.mail-archive.com/[EMAIL PROTECTED]/thrd3.html -----Original Message----- From: David Nagrosst [mailto:[EMAIL PROTECTED] Sent: 24 March 2003 17:14 To: [EMAIL PROTECTED] Subject: Mod_jk and tomcat 4.1.18 communication issues I have plenty of processors for ajp13 running under tomcat, but tomcat and mod_jk seem to lose communication and when that happens the tomcat process gets stuck running at 99% cpu utilization. This occurs when I am just bouncing around the site for a while. When the page gets stuck(does not load all the way) within that session and I refresh, I get another stuck process. It's very strange. when I run the site through port 8080, it works fine. No problems. Mod_jk2 does not cause problems, but does not load index file automatically, which is why I am using mod_jk in the first place. Any help is greatly appreciated. Thanks in advance, David excerpt from server.xml <Connector className="org.apache.ajp.tomcat4.Ajp13Connector" port="8009" minProcessors="20" maxProcessors="200" enableLookups="false" connectionTimeout="60000" useURIValidationHack="false" acceptCount="10" debug="1"/> excerpt from web.xml <servlet> <servlet-name>jsp</servlet-name> <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class> <init-param> <param-name>logVerbosityLevel</param-name> <param-value>WARNING</param-value> </init-param> <init-param> <param-name>development</param-name> <param-value>false</param-value> </init-param> <init-param> <param-name>reloading</param-name> <param-value>false</param-value> </init-param> <init-param> <param-name>compiler</param-name> <param-value>jikes</param-value> </init-param> <load-on-startup>3</load-on-startup> </servlet> excerpt from workers.properties worker.ajp13.port=8009 worker.ajp13.host=localhost worker.ajp13.type=ajp13 # # Specifies the load balance factor when used with # a load balancing worker. # Note: # ----> lbfactor must be > 0 # ----> Low lbfactor means less work done by the worker. worker.ajp13.lbfactor=1 # # Specify the size of the open connection cache. worker.ajp13.cachesize=100 worker.ajp13.socket_keepalive=1 except from mod_jk.conf JkMount /*.jsp ajp13 /var/log/httpd/mod_jk.log [Mon Mar 24 11:57:17 2003] [jk_ajp_common.c (970)]: ERROR sending data to client. Connection aborted or network problems [Mon Mar 24 11:57:17 2003] [jk_ajp_common.c (970)]: ERROR sending data to client. Connection aborted or network problems [Mon Mar 24 11:57:17 2003] [jk_ajp_common.c (970)]: ERROR sending data to client. Connection aborted or network problems [Mon Mar 24 11:57:17 2003] [jk_ajp_common.c (681)]: ERROR: can't receive the response message from tomcat, network problems or tomcat is down. [Mon Mar 24 11:57:17 2003] [jk_ajp_common.c (1050)]: Error reading reply from tomcat. Tomcat is down or network problems. [Mon Mar 24 11:57:17 2003] [jk_ajp_common.c (1187)]: ERROR: Receiving from tomcat failed, recoverable operation. err=0 [Mon Mar 24 11:57:18 2003] [jk_ajp_common.c (970)]: ERROR sending data to client. Connection aborted or network problems [Mon Mar 24 11:57:18 2003] [jk_ajp_common.c (970)]: ERROR sending data to client. Connection aborted or network problems [Mon Mar 24 11:57:18 2003] [jk_ajp_common.c (681)]: ERROR: can't receive the response message from tomcat, network problems or tomcat is down. [Mon Mar 24 11:57:18 2003] [jk_ajp_common.c (1050)]: Error reading reply from tomcat. Tomcat is down or network problems. [Mon Mar 24 11:57:18 2003] [jk_ajp_common.c (1187)]: ERROR: Receiving from tomcat failed, recoverable operation. err=0 [Mon Mar 24 11:57:18 2003] [jk_ajp_common.c (970)]: ERROR sending data to client. Connection aborted or network problems catalina.out Ajp13Connector active threads=21 java.lang.ThreadGroup[name=Ajp13Connector[8009],maxpri=10] Thread[Ajp13Connector[8009],5,Ajp13Connector[8009]] Thread[Ajp13Processor[8009][0],5,Ajp13Connector[8009]] Thread[Ajp13Processor[8009][1],5,Ajp13Connector[8009]] Thread[Ajp13Processor[8009][2],5,Ajp13Connector[8009]] Thread[Ajp13Processor[8009][3],5,Ajp13Connector[8009]] Thread[Ajp13Processor[8009][4],5,Ajp13Connector[8009]] Thread[Ajp13Processor[8009][5],5,Ajp13Connector[8009]] Thread[Ajp13Processor[8009][6],5,Ajp13Connector[8009]] Thread[Ajp13Processor[8009][7],5,Ajp13Connector[8009]] Thread[Ajp13Processor[8009][8],5,Ajp13Connector[8009]] Thread[Ajp13Processor[8009][9],5,Ajp13Connector[8009]] Thread[Ajp13Processor[8009][10],5,Ajp13Connector[8009]] Thread[Ajp13Processor[8009][11],5,Ajp13Connector[8009]] Thread[Ajp13Processor[8009][12],5,Ajp13Connector[8009]] Thread[Ajp13Processor[8009][13],5,Ajp13Connector[8009]] Thread[Ajp13Processor[8009][14],5,Ajp13Connector[8009]] Thread[Ajp13Processor[8009][15],5,Ajp13Connector[8009]] Thread[Ajp13Processor[8009][16],5,Ajp13Connector[8009]] Thread[Ajp13Processor[8009][17],5,Ajp13Connector[8009]] Thread[Ajp13Processor[8009][18],5,Ajp13Connector[8009]] Thread[Ajp13Processor[8009][19],5,Ajp13Connector[8009]] =================================== --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
