This content has been marked as final. Show 4 replies
Can mention information about OS and JDK? Are you using Java Hotsspot or Jrockit?
The OS is RedHat Linux X86-64 (version 2.6.18-308.24.1.el5) and JDK version is 1.6.0_24
Edited by: user1082176 on Mar 13, 2013 12:05 PM
Hi Kanchan,1 person found this helpful
Few things you could do here is,
1. Check GC logs to check if Garbage collector selected is able to release un-referenced objects. Logs will give you hint about possible memory leak.
If you have not set debug GC logs then set it using -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintGCApplicationStoppedTime -XX:+PrintGC -Xloggc:/logs/server1_gclogs.txt
2. Would prefer to take heap dump on OOM and use any tool like jhat or MAT to analyse. It will help in deciding if you require any performance tuning at JVM level. sometime it happens that heap space allocated is tool low causing OOM.
For taking heap dump either set it as JAVA option - "*-XX:+HeapDumpOnOutOfMemoryError*"
using Sun tool "jmap"
$ jmap –heap:format=b <pid>
The information in the post hints that you might have problems with memory leaks. Find out whether you have any by using [http://plumbr.eu] - it is the easiest way to find the cause of a memory leak.
Let me know if you have any further questions or problems with the potential leak detection.