Paul Mansfield a �crit : > > typically, I tried a random variation of my searches on google and > came up with an answer: > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg111708.html > > these suggest that tomcat itself causes memory leaks, and is > exacerbated by jetspeed's leaks.
I've just read this mail and see this : > From: William Connor > Subject: Re: Tomcat 4.0.x memory leak (not javac) > Date: Wed, 03 Dec 2003 09:09:37 -0800 > > We first ran into this bug when hot-deploying JetSpeed - about seven > times would cause an out of memory w/ the default heap size. > JetSpeed had so many leaks itself that we dropped down to bares bones > test app with a servlet, but no JSPs or third party libraries. Jetspeed has so many leaks ??? We've made some tests over here for potential leak and didn't find anything alarming. The only stuff that was potentially leaking was the Tool object from velocity, staying in memory even after a request is done, we didn't really understand how to use it so we plan not to use it anymore. Did anyone ever really meet those memory leak, or is it more the portlets developped by a end-user that could leak... ? That's just cause I was a little afraid of those lines, but already seen so many people yelling at opensource projects saying it was leaking where it wasn't that I'd like any end-user real experience. Tell me someone already had a jetspeed portal running for a long time ??? :) Aurelien --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
