[from your blog entry]
> I also think that logging leaks may be more helpful than using part of
> manager, because many don't deploy manager (they remove it).
it is logged when the application is stopped, on recent tomcat 6 and 7.
I think your approach to finding leaks by performing comparisons i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gary,
On 5/10/2011 4:33 PM, Gary Weaver wrote:
> Chris,
>
> On Tue, May 10, 2011 at 4:06 PM, Christopher Schultz <
> ch...@christopherschultz.net> wrote:
>
>>
>> http://people.apache.org/~markt/presentations/2010-11-04-Memory-Leaks-60mins.pdf
>
> Than
binLmaU7goP1J.bin
Description: PGP/MIME version identification
On 5/10/11 8:55 PM, Gary Weaver wrote:
> Here's what I did and what little I came up with:
> http://stufftohelpyouout.blogspot.com/2011/05/diagnosing-webappportlet-hot-deploy.html
>
> I'm definitely not an expert at diagnosing leaks, so if you have any
> recommendations/comments, please let me kno
Chris,
On Tue, May 10, 2011 at 4:06 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
>
> http://people.apache.org/~markt/presentations/2010-11-04-Memory-Leaks-60mins.pdf
>
Thanks! That is a great presentation!
Gary
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gary,
On 5/10/2011 3:55 PM, Gary Weaver wrote:
> http://stufftohelpyouout.blogspot.com/2011/05/diagnosing-webappportlet-hot-deploy.html
Generally speaking, when you have a permgen "leak" across webapp
redeployments, this is the situation:
1. Webapp
Here's what I did and what little I came up with:
http://stufftohelpyouout.blogspot.com/2011/05/diagnosing-webappportlet-hot-deploy.html
I'm definitely not an expert at diagnosing leaks, so if you have any
recommendations/comments, please let me know.
I unfortunately started off just thinking I c
