> From: Martin Gainty [mailto:mgai...@hotmail.com]
> Subject: RE: Redeploy leaks
>
> > http://community.eapps.com/showthread.php?t=153
> MG>good link to illustrate PermGen settings but including
> class objects in sweep for recovering PermGen should be a
> last MG&
MG>Mark/Raul/Frank
> Yes, you should be cooked, sauted and broiled on an open flame .
MG>this comment does not help
> http://community.eapps.com/showthread.php?t=153
MG>good link to illustrate PermGen settings but including class objects in
sweep for recovering PermGen should be a last MG>reso
Yes, you should be cooked, sauted and broiled on an open flame .
http://community.eapps.com/showthread.php?t=153
Take a look, maybe useful
On Tue, Jan 6, 2009 at 9:34 AM, Mark Hagger wrote:
> On Sat, 2009-01-03 at 14:30 -0500, Cosio, Raul wrote:
> > Memory leak is an advanced task. But once und
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
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
de-registering jdbc driver, 2) shutdown log4j after use.
To de-register jdbc driver just put this code in the contextDestroyed()
method inside a ServletC
Kees Jan Koster wrote:
Dear Adriano,
As I had having OutOfMemory exceptions (PermGen) when redeploying an
application, I started to verify things using Eclipse Memory Analyzer.
I've discovered some real leaks, for example caused by the Java
Disposer thread being instantiated using the Webapp
Dear Adriano,
As I had having OutOfMemory exceptions (PermGen) when redeploying an
application, I started to verify things using Eclipse Memory Analyzer.
I've discovered some real leaks, for example caused by the Java
Disposer thread being instantiated using the Webapp classloader.
After
