Try this in your jk2.properties file and see if it fixes it for 4.1.29. According to Bill Barker(thread: "maxProcessors vs maxThreads"), this is the same as the 5.x connector setting for jk2.
container.maxThreads=<value> container.maxSpareThreads=<value> container.minSpareThreads=<value> Unfortunately I do not have time to mess with this right now, but I am interested to know if it fixes the leak. Charlie > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of David Strupl > Sent: Monday, January 19, 2004 2:08 PM > To: [EMAIL PROTECTED] > Subject: Re: out of memory problem. Help! > > This did not work for me in 4.1.29 since the only way to do this is to > set minProcessors==maxProcessors but that did not have any effect in > 4.1.29. I am not sure whether I could use xxxThreads there but > downgrading to 4.1.27 did help. > > For those using 5.0.16 this can help - Filip thanks for finding out. > > Best, > > David > > Filip Hanik wrote: > > set maxSpareThreads=minSpareThreads=maxThreads will cause the system to > > never shrink the pool > > > > Filip > > > > -----Original Message----- > > From: news [mailto:[EMAIL PROTECTED] Behalf Of David Strupl > > Sent: Monday, January 19, 2004 9:58 AM > > To: [EMAIL PROTECTED] > > Subject: Re: out of memory problem. Help! > > > > > > Remy Maucherat wrote: > > > >>This is not true: there's indeed a memory leak with 5.0.16, but it would > >>occur only with specific traffic patterns. It will not bring a server > >>down in just a few requests. > > > > > > Indeed. The thread pool has to grow and shrink for this to happen. > > Unfortunatelly quite common e.g. day and night traffic. > > > > D. > > > > > > > > --------------------------------------------------------------------- > > 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]
