Hi 

Thanks for your comments.

>You should have a look in the server.xml file and at your httpd.conf to see
>if it is similar like this :
>(maxTheads should be the same as the apache threads)
>
>        <Ajp13Connector port="8009"
>                          maxThreads="150"
>                          maxSpareThreads="50"
>                          minSpareThreads="10" />
>
>(thanx Henri..)

We haven't used AJP13 since mod_webapp is the supposed to be the preferred method with 
TC 4.0.1. We used AJP12 with TC 3.2.3 and set the parameters as you show. We still got 
the same 
problems so we're not overconfident that AJP13 will fix them.

Interesting to read what you say about the restarts - I'll try restarting TC with no 
Apache restarts. 

On the session timeout, I have that set to 10 minutes (from the default 30). If there 
is one thread per session then maybe I ought to go to 5 minutes or less ! Where is the 
parameter that govens how 
often the session are checked. In Apache JServ, I recall something like checkInterval 
in the zone.properties file. Maybe TC4 is cleverer onthat one.


Chris

>Advice is anyway  to run jdk13 instead of the ajp12 you specified.
>
>> 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 ?
>
>Hmm.. don't know if it has these parameters, but the cvs version of
>mod_webapp automatically tries to "deploy" an webapp when it is not
>available directly after startup (which means : you can start apache after
>tomcat or restart tomcat any time you like).
>
>> 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 ?
>
>Your session timeout is probably 30 minutes. As far as I know, every session
>has is thread.. So that might explain the high number of threads..
>
>Mvgr,
>Martin
>
>
>--
>To unsubscribe:   <mailto:[EMAIL PROTECTED]>
>For additional commands: <mailto:[EMAIL PROTECTED]>
>Troubles with the list: <mailto:[EMAIL PROTECTED]>
>
>




--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Reply via email to