ay, May 29, 2003 5:45 PM
Subject: Re: Java can leak...
> We need to do more investigation on our side for sure, I just wanted
to
> know if anyone had noticed memory leaks over long recycled
connections.
> The JVM my app runs in alots 768Mb as the max, but I work in
conjunction
>
Jan,
Let me elaborate. No doubt one can still do silly things in Java that may lead to
severe memory problems. However, the point I was trying to make is that Java
applications do not 'leak' memory in a way non-GC applications do. One can easily
starve a java application of heap memory if objec
We need to do more investigation on our side for sure, I just wanted to
know if anyone had noticed memory leaks over long recycled connections.
The JVM my app runs in alots 768Mb as the max, but I work in conjunction
with serveral apps. I'm the only app using HttpClient. When I run and
I rea
My impression of your first email was that the server had used up the
4GB of memory. Are you saying it was HttpClient? If so, you must have
run the JVM and specified the max heap size to something like -Xmx4GB.
If that's the case then this is probably something you don't want to
do. Once Ja
I think the reality here is that the only way to reliably track down
the problem is to actually profile the original application that is
seeing the problem. There's really not a lot of point in me profiling
HttpClient separately because I've not seen any problem with memory
leaks so they'r
Jan,
Good point. With Java you don't have to remember as much about silly things like
malloc and free in C/C++ which led to all sorts of problems.
However, you do have to worry about GC, object creation and holding on to objects for
too long.
Something like HPJMeter may help in analyzing the
