Last week I was stress testing a webapplication. While putting heavy load to the server, the server went Oom (Out Of Mana… , euh Memory) . That was a quick stress test. The testing task quickly changed into a debugging task.
Finding the leak isn’t an easy task. With just looking at a java.lang.OutOfMemoryError error you wont find it. You’ll need a profiler or a heapdump inspection tool.
I decided to go for the profiler. A year ago I tried the netbeans internal profiler, that was a very nice profiler but it’s a pain to import projects into NB that don’t follow it’s standards. So this time, no NetBeans.
Continue reading “Memory Profiling On Applications”