Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Why isn't VisualVM showing all the normal tabs?

Usually I see all these tabs in VisualVM for locally running Java programs:

enter image description here

However, I have one local program which is currently only showing me Overview and Monitor (even though it usually shows all those shown above):

enter image description here

Also interesting is that VisualVM itself doesn't present the Profile tab:

enter image description here

All three of the programs shown are running with the same JVM with the same Java Home.

What controls which tabs are shown for a particular program? How can I get them all back for my program showing just Overview and Monitor?

I have Visual VM 1.3.5 (latest at this date) and JDK 1.7.0_17.

like image 841
jwl Avatar asked Apr 15 '13 19:04

jwl


People also ask

Does VisualVM work with Java 11?

Use VisualVM bundled with GraalVMGraalVM contains a fully compliant Java SE 8, Java SE 11, and Java SE 17 JDK distribution based on Oracle JDK and OpenJDK. It features an innovative JIT compiler which may noticeably improve performance of Java applications, compared to the standard Oracle JDK or OpenJDK.

What is difference between JConsole and VisualVM?

VisualVM takes application monitoring one level deeper than JConsole by allowing the user to analyze thread execution as well as the ability to profile CPU and memory usage of JVM requests, both of which are triggered manually by the user.

How do I add apps to VisualVM?

To install a VisualVM plugin:Choose Tools > Plugins from the main menu. In the Available Plugins tab, select the Install checkbox for the plugin. Click Install. Step through and complete the plugin installer.

Is VisualVM part of OpenJDK?

Neither in Ubuntu nor in Debian the tool visualvm is part of the OpenJDK 7 package. It's part of the Oracle JDK 7 and seems to be GPL licensed. While in Ubuntu it can be installed with a separate package, such a package doesn't exist in Debian.


1 Answers

I found that this was the issue of usage of wrong JDK version. In my case my application was running on 64bit JDK and I started VisualVM from 32bit JDK. After starting VisualVM from the same JDK on which my application is running, everything was fine. Hope it will help you.

like image 128
user613114 Avatar answered Sep 20 '22 12:09

user613114