VisualVM: The new all-in-one troubleshooting tool for the Java platform

At JavaOne this year we showed a first prototype of a new all-in-one troubleshooting tool for the Java platform named VisualVM.

We promised that we would make it public as soon as we could and the time has come.

Go to the VisualVM project on java.net, download the new tool, give it a try and send us feedback.

Have fun!

Comments:

Hello,

Does this VisualVM application uses Java APIs such as hat to provide profiling?
Are there any other Java APIs that enable heap inspection.

Thanks,

Kiev Gama

Posted by Kiev Gama on November 03, 2007 at 02:25 PM CET #

VisualVM uses the jvmstat (http://java.sun.com/performance/jvmstat/index.html) and JFluid (http://profiler.netbeans.org/jfluid.html)
technologies for monitoring and profiling and the new attach (http://java.sun.com/javase/6/docs/jdk/api/attach/spec/index.html)
technology for obtaining heap dumps.

The built-in HeapWalker in VisualVM and the jhat tool in JDK 6 can analyze heap dumps in HPROF binary format.

Posted by Luis-Miguel Alventosa on November 05, 2007 at 03:28 AM CET #

Thanks Luis Miguel!

I've read your first blog post. I'm at Grenoble too, I study at Grenoble I (UJF).

I doing some stuff for my masters project in which I wanted to check from the current running application its allocation tree based on queries constructed on the fly.
I could do that with jhat using its API and simple OQL queries. It is kind of awkward since I need to run jmap via Runtime.exec, and later use that library, which I would not be surprised if it changed or disappeared in Java 7. There is other ugly stuff too like getting the PID of the running Java app, if you could give me a "official" way to get it would be glad ;)

Thanks again.
Regards,

Kiev

Posted by Kiev Gama on November 05, 2007 at 12:25 PM CET #

Hi Kiev,

If you're running on JDK 6 then you should not need to run jmap with Runtime.exec(). Instead you could attach to the target VM using the new Attach API, start the out-of-the-box JMX management agent (if not already running) and invoke the dumpHeap operation on the com.sun.management.HotSpotDiagnostic MXBean and then use jhat on the HPROF binary file.

Use the jps command or the Attach API itself to get the list of running VMs (belonging to you). If you are obtaining the heap dump from the running application itself then you don't need the PID, just call dumpHeap on the HotSpotDiagnostic MXBean.

For more detailed info have a look at the Monitoring and Management guide at http://java.sun.com/javase/6/docs/technotes/guides/management/index.html

Posted by Luis-Miguel Alventosa on November 05, 2007 at 03:06 PM CET #

Thanks for your information, i have read it, very good!

Posted by cheap ed hardy on November 01, 2009 at 05:36 PM CET #

Post a Comment:
  • HTML Syntax: NOT allowed
About

lmalvent

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today