Hello We've been running Apache 1.3.12 and Tomcat (3.2.3 and 4.0.1), to service servlet content. We are using Sun's JDK 1.3.0_02 on Linux (RedHat). We are finding that the site runs reasonably well but we see that the number of JDK processes rises over a period of time and when it reaches over 120, it tends to lock up Apache - at which point we have to restart the whole site.
On Tomcat 3.2.3, we used the AJP12 connector and used the parameters for the minimum and maximum spare servers - all to no effect. With Tomcat 4.0.1, we are using the mod_webapp connector but I'm not sure whether there are similar parameters, the page at http://jakarta.apache.org/tomcat/tomcat-4.0-doc/config/warp.html isn't finished.Can anyone tell me whether there are similar parameters ? The site gets about 250,000 to 300,000 hits per day (most of which just goes through Apache) and about 15000 requests of the various servlets. Is there anything we can do to limit the way that the JVM/ JDK processes rise ? Is there anything in the servlets which might be causing this ? IN Tomcat 3, we had a cron job which monitored the jdkprocesses and occassionally restarted Tomcat. No doubt people out there are wincing now,but hey, it worked !InTomcat 4,it looks like the same job won't work because in TC4, youhave to restart Apache everytime TC4 is restarted. Chris -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
