Re: Found it - WAS: Memory leak

[Jess Holle]

This sort of memory leak can't be left unaddressed -- i.e. you shouldn't 
have to change the settings to avoid an intolerable memory leak.

Is this issue new to 5.0.17 or was it in 5.0.16 as well?  In either 
case, it would be good to see this fixed in 5.0.17 -- but it is all the 
more critical if it was initially broken in 5.0.17!

--
Jess Holle
Filip Hanik wrote:

I dont think setting maxSpareThreads==maxThreads is a good solution to a
problem as this memory leak. I still have to verify that that would actually
solve the problem
if we don't want to remove request info, lets fix it.
Filip

-----Original Message-----
From: Remy Maucherat [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 15, 2004 5:24 AM
To: Tomcat Developers List
Subject: Re: Found it - WAS: Memory leak
Remy Maucherat wrote:
 

-1. There is no memory leak with this.
ByteChunks/CharChunks are always reused. If new ones are created, they
will be reused.
   

Arg, I have to find something.
I know ! It's all Costin's fault !
I didn't think about the "scaling back" feature of the thread pool, to
be honest. It should be very easy to avoid the problem, by setting
maxSpareThreads to maxThreads.
Rémy



---------------------------------------------------------------------
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]