peter cooke wrote:
from a developer perspective " have jprobe watch a stress test version of the app and hope it get it"
Hoping is generally not a good debugging technique.... well, it may work, but it's not a technique...
You need to really understand your application too. For example, you put a profiler on the application, and it says there is a million instances of class Foo, is it a memory leak? Or is the application supposed to have a million instances?
And a leak doesn't have to show up as one instance type. It could be a steady growth of many instance types. You need to understand how your program is supposed to grow based on usage.