Java.lang.OutOfMemoryError - reasons

Question

Hi
My application is throwing
Wed Mar 26 15:07:12 PST 2003:<E> <ServletContext-General> Servlet failed with
Exception
java.lang.OutOfMemoryError
<<no stack trace available>>
Wed Mar 26 15:07:12 PST 2003:<E> <Kernel> ExecuteRequest failed.
java.lang.OutOfMemoryError
<<no stack trace available>>
exception and hangs. At the time of this exception, my verbosegc shows
[GC 198159K->168522K(523136K), 0.0737788 secs]
So, it means I have enough JVM memory to run my application (correct me if I am
wrong). Then what could be reason for my application to throw OutOfMemory exception.
I though that my application is having some memory leak and thats why whenever
Full GC happens, its not freeing up JVM memory. But now I found that, when GC
or Full GC happens, it releases lot of memory back.
Please help me
Thanks
V Prakash

Answer 1

Thank you.
I am going to go with newSize and MaxnewSize=64m initially. Lets see.
"Kenneth A Kauffman" <[email protected]> wrote:
>
"Prakash" <[email protected]> wrote in message
news:3e8344bd$[email protected]..
My application runs on WLS 5.1 and jdk1.3. Thanks.
"Prakash" <[email protected]> wrote:
Hi
My application is throwing
Wed Mar 26 15:07:12 PST 2003:<E> <ServletContext-General> Servlet
failed
with
Exception
java.lang.OutOfMemoryError
<<no stack trace available>>
Wed Mar 26 15:07:12 PST 2003:<E> <Kernel> ExecuteRequest failed.
java.lang.OutOfMemoryError
<<no stack trace available>>
exception and hangs. At the time of this exception, my verbosegc shows
[GC 198159K->168522K(523136K), 0.0737788 secs]
So, it means I have enough JVM memory to run my application (correct
me if I am
wrong). Then what could be reason for my application to throw OutOfMemory
exception.
I though that my application is having some memory leak and thatswhy
whenever
Full GC happens, its not freeing up JVM memory. But now I found that,
when GC
or Full GC happens, it releases lot of memory back.
Please help me
Thanks
V PrakashTune your heap. Start the server with the following:
-Xms=512m -Xmx:512m -XX:PermSize=32m -verbose:gc -XX:NewSize=128m -XX:MaxNew
Size=128m
Then observe GC collections and see if it fails.
ken kauffman