> From: Greg McCane [mailto:gregmcc...@yahoo.ca]
> Subject: Re: Tips on tracking down memory leaks
>
> Is there any danger in taking a heap dump on our system running in
> production? Will it cause a significant performance hit or other nasty?
No; taking a heap dump will cause a
1:31:16 PM
Subject: RE: Tips on tracking down memory leaks
> From: Greg McCane [mailto:gregmcc...@yahoo.ca]
> Subject: Tips on tracking down memory leaks
>
> The memory growth appears to be in large chunks rather
> than slow, steady growth.
Use a heap profiler to find out what'
Thanks a lot Joe, we are checking our code based on your suggestions.
Cheers,
Greg
From: Joseph Morgan
To: Tomcat Users List
Sent: Tue, January 12, 2010 11:15:54 PM
Subject: RE: Tips on tracking down memory leaks
Greg, you've just awakened a 900 lb go
2010 11:31:16 PM
Subject: RE: Tips on tracking down memory leaks
> From: Greg McCane [mailto:gregmcc...@yahoo.ca]
> Subject: Tips on tracking down memory leaks
>
> The memory growth appears to be in large chunks rather
> than slow, steady growth.
Use a heap profiler to find out w
> From: Greg McCane [mailto:gregmcc...@yahoo.ca]
> Subject: Tips on tracking down memory leaks
>
> The memory growth appears to be in large chunks rather
> than slow, steady growth.
Use a heap profiler to find out what's eating up the space and who is
allocating it. Even the simple one (hprof)
Greg, you've just awakened a 900 lb gorilla!
My guess, based upon your description of the problem as large chunks at
a time, is something related to reading and caching data, and this is
why PMD and profiling tools won't help.
Therefore, look at all the code accessing data from whatever storage
