I consider old code part of application code :) no age discrimination
when it comes to memory leaks.
>> What you describe in your memory graph is a simple memory leak.
>> Generally, I would look in that order:
>
> 1a. Old code? Look for improperly closed DB connections.
>
>> 1. Sessions
>> 2
On 16/11/2009 23:54, Elli Albek wrote:
You can try getting an object dump from a profiler and see which
objects are the source of memory starvation. Simple JSPs are very
unlikely to cause memory starvation, but you mentioned “application
code”, which implies that you have more than simple JSPs.
> From: kulbir Saini [mailto:kulbir.sai...@gmail.com]
> Subject: Java Out of Heap Issue
>
> just a snapshot of jmap,
Try using jhat to actually see what's consuming the space in the heap.
> Heap Configuration:
>MaxNewSize = -65536 (-0.0625MB)
That looks suspicious...
> Heap Usage:
>
What I have found works well in some circumstances where you do not have
a profiler to hand.
1. Look for static declarations in your code that point to singletons or
collection objects. They might just grow and grow
2. You may not be using third party libs correctly, e.g. Not closing
connection
You can try getting an object dump from a profiler and see which
objects are the source of memory starvation. Simple JSPs are very
unlikely to cause memory starvation, but you mentioned “application
code”, which implies that you have more than simple JSPs.
A few things you want to cross off your p
