> -----Original Message----- > From: Rainer Jung [mailto:rainer.j...@kippdata.de] > Sent: Thursday, May 21, 2009 3:37 PM > To: Tomcat Users List > Subject: Re: Running out of tomcat threads - why many threads in > RUNNABLEstage even with no activity > > On 22.05.2009 00:19, Pantvaidya, Vishwajit wrote: > > [Pantvaidya, Vishwajit] I will set > > - cachesize=1 (doc says jk will autoset this value only for worker-mpm > and we use httpd 2.0 prefork) > > You don't have to: "JK will discover this number for the Apache web > server automatically and set the pool size to this value".
[Pantvaidya, Vishwajit] Does what you say hold true for jk 1.2.15 also? Because I saw that for the 1.2.15 cachesize directive, http://tomcat.apache.org/connectors-doc/reference/workers.html#Deprecated%20Worker%20Directives says that "JK will discover the number of threads per child process on Apache 2 web server with worker-mpm and set its default value to match the ThreadsPerChild Apache directive.". Since we use pre-fork MPM, I assumed we need to set cachesize. > > - remove cache and recycle timeouts > > Chris and me are not having the same opinion here. You can choose :) > [Pantvaidya, Vishwajit] I think that may be only because my adding the connectionTimeout led you to believe that I wanted nonpersistent conn's. Now that I know persistent connections are better, I am trying to rollback connectionTimeout - and then I guess you will agree with Chris that I need to rollback the recycletimeouts, etc in workers file on httpd side also? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
