Trying this out to analyze memory usage and find leaks in Java application:
http://blog.emptyway.com/2007/04/02/finding-memory-leaks-in-java-apps/
Pretty slick...
In Eclipse for my debug configuration I put this in the vm arguments box:
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=9000
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-agentlib:hprof=heap=dump,file=/tmp/hprof.bin,
format=b,depth=10
A few more details for those not so familiar with Java:
jconsole.exe is found in the /bin directory in the directory where you installed the Java JDK. It is an application with a GUI so just double click on it to open it up. You then select your application from the list to view details about it.
jps.exe is run from command prompt. It is also found in the /bin directory in the directory where you installed the Java JDK. Go to a command prompt (start menu, run, enter "cmd" hit enter) and navigate to that bin folder or alternatively you can type out the full path to jps.exe to run it.
jmap.exe is also in the /bin directory. You also would run that from the command line by typing in the location where you want to write the file and the process id as described in the above article.
jmap -dump:format=b,file=/tmp/java_app-heap.bin 15976
Once that file is created,run jhat as directed.
jhat -J-Xmx326m /tmp/java_app-heap.bin
Then in browser go to:
http://localhost:7000
You can browse that data to find which objects are most in use, how much memory they are taking up, etc.
If a very slow leak can run the app in production using the above to output file over time and then view it.
Seems like support for Eclipse Memory Analyzer and Eclipse TPTP are dwindling but this method above is pretty simple.
