Hpjmeter Memory leak

[nagasreekrishna]

Does anybody know what is the algorithm that is used by the HP Jmeter to find out the memory leaks

[Dennis Handly]

Here is some info I received:
There are 2 modes of running HPjmeter - live monitoring (dynamic analysis) and static analysis (after the fact).

In live monitoring, HPjmeter keeps track of the heap usage over time. If there is an upward trend in heap usage over time (as determined by the memory level after a Full GC has taken place), HPjmeter assumes that there is some kind of memory leak in the java heap, and various alerts will trigger (depending on what you have set for your trigger point). HPjmeter also tracks the java collection classes and will indicate if it thinks one of those classes is the cause of the leak.

With static analysis, you can run the application with java option
-Xverbosegc and view the results in HPjmeter later. After the application should have reached steady-state, and you still observe an upward trend in the memory level after Full GCs, then you have a leak in the java heap. To determine the cause, you can take heapdumps at selected intervals, read them into HPjmeter, and determine which object is causing the leak.

For additional documentation, you can refer to the HPjmeter Users' Guide:
http://docs.hp.com/en/5992-0757/index.html
or go to www.hp.com/go/hpjmeter