tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Hagger <>
Subject RE: Redeploy leaks
Date Tue, 06 Jan 2009 14:34:12 GMT
On Sat, 2009-01-03 at 14:30 -0500, Cosio, Raul wrote:
> Memory leak is an advanced task. But once understood is very easy to fix
> them, just follow some simple rules, most common situations are: 1) Not

Usually a matter of torturing yourself for some time following
classloader trees, together with various static instantiations.  Logging
systems and Axis/jakarta-commons stuff have been the main causes of
problems for me.

This article was useful for me:

I suppose that they are very easy to fix once you work out precisely
what is causing a leak, but that's a bit like saying that most bugs are
very easy to fix - but thats a bit misleading isn't it, since you could
spend hours/days tracking down the bug in the first place.

Although its obviously nice to track down all the leaks in your app so
that you could sit redeploying all day to your hearts content (I'll
probably be burned at the stake for this next bit) but I do sometimes
suspect that its not worth the effort and just live with having to
restart your tomcat instance from time to time depending on your
redeploy strategies.


This email has been scanned for all known viruses by the MessageLabs SkyScan service.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message