I have recently reinstalled Windows and I am using JDK 1.8 u91 with the built-in VisualVM. I have checked my proxy settings to ensure that they are all off, both in Windows proxy settings and within the proxy settings of VisualVM.
I have also tried reinstalling JDK, restarting computer, reinstalling Windows. I only have one JDK installed and the classpath is set to the JDK's bin folder in Windows.
All features besides CPU and memory profiling work in VisualVM. My application is ran from IntelliJ, but I have also tried running applications regularly from command line and VisualVM cannot connect to those either.
I have also tried downloading VisualVM off http://visualvm.java.net which also does not work.
I have no plugins installed.
Why does it hang? Is this is a bug introduced with the new JDK?
See this bug report - VISUALVM-637
Solution: start JVisualVM using below command :
jvisualvm.exe -J-Dorg.netbeans.profiler.separateConsole=true
I've checked this (and it works !) at Windows 10 X64 with java version "1.8.0_102"
Try starting the (local) application to observe with additional:
-Djava.rmi.server.hostname=localhost
来源:https://stackoverflow.com/questions/37632783/visualvm-cpu-memory-profiler-stuck-at-connecting-to-the-target-jvm