Pinned topicWasce doesnt free memory

‏2012-10-29T14:33:03Z
|Tags:

Answered question
This question has been answered.

Unanswered question
This question has not been answered yet.

Hello,

I'have an application running in a server WASCE, and i have to restarted it twice or three times a day because it seems not to free memory, the JVM has 2,7 Go assigned and when the memory arrive a 2,3 Go le application crash!

Could someone know why is this happened, i ask the developpement team, and of course, it is not the application.....
Build 2.1.0.1-20080825
Start Time Mon Oct 29 15:00:21 MET 2012
Up Time 14 minutes 22 seconds

Re: Wasce doesnt free memory

Re: Wasce doesnt free memory

‏2012-11-09T13:01:12Z

This is the accepted answer.
This is the accepted answer.

Hi,
The only thing i can see is the memory increasing until almost the Total Memoty Allocated, and the wasce server stop, if i watch Full GC at this moment, it takes JMV a lot of time free memory, and sometimes is recover and sometimes goes down and i have to restart it.
I have dynatrace but i am not capable to get some clear information...

Re: Wasce doesnt free memory

Hi,
The only thing i can see is the memory increasing until almost the Total Memoty Allocated, and the wasce server stop, if i watch Full GC at this moment, it takes JMV a lot of time free memory, and sometimes is recover and sometimes goes down and i have to restart it.
I have dynatrace but i am not capable to get some clear information...

It sounds like there is a memory leak in your server. The most likely cause is your application code. However, there could be a problem in WAS CE, itself. Looks like you have an old version of WAS CE. Would also be a good idea to upgrade to the latest version of WAS CE 2.1 (or 3.0).

If you have licensed WAS CE support, you should open a PMR. Otherwise, you'll need to investigate the problem, yourself.

The Sun JVM parameter "-XX:+HeapDumpOnOutOfMemoryError" will cause the Sun JVM to generate a HeapDump on an OutOfMemoryError. You can then use a variety of tools to read this heapdump and understand what objects are not being GC'ed. There are also a number of tools which can be used to attach to a running server.

One tool that can be used to analyze heapdumps is http://www.eclipse.org/mat/.

Re: Wasce doesnt free memory

It sounds like there is a memory leak in your server. The most likely cause is your application code. However, there could be a problem in WAS CE, itself. Looks like you have an old version of WAS CE. Would also be a good idea to upgrade to the latest version of WAS CE 2.1 (or 3.0).

If you have licensed WAS CE support, you should open a PMR. Otherwise, you'll need to investigate the problem, yourself.

The Sun JVM parameter "-XX:+HeapDumpOnOutOfMemoryError" will cause the Sun JVM to generate a HeapDump on an OutOfMemoryError. You can then use a variety of tools to read this heapdump and understand what objects are not being GC'ed. There are also a number of tools which can be used to attach to a running server.

One tool that can be used to analyze heapdumps is http://www.eclipse.org/mat/.