On 7/29/06, devel - Fashion Content <[EMAIL PROTECTED]> wrote:
I find memory leaks to be a complete showstopper. I like to do a lot of iterative modifications on a test webserver. My current setup lasts about 5-10 redeploys before Tomcat runs out of memory. It makes the whole thing look very fragile.
There are many factors that can contribute to memory leaks. I recently found that on our main server, there are no leaks on redeployment! Even the permgen space stays ok. With a proper configuration, it is possible to prevent most memleaks issues. There are none that I'm aware of in T4 + tomcat (I did quite a bit of heap analysis). If the framework has thread safety issues, is that something that can be
fixed by patching it ?
The root of all of that are classloading issues with webapps but this is well documented with commons logging and all the tapestry devs seem to know that stuff well. Henrik
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Henri Dupre Actualis Center
