jvisualvm

Closed. This question is off-topic. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it's on-topic for Stack Overflow. JConsole has quiet a buggy view to monitor JMX published counters. What are the other alternatives ? I am unable to find any, other than JVisualVM which in effect uses the same view Some alternatives are (since I'm fine with JVisulaVM I haven't tried them yet): JRockit Mission Control (will be added as Java Mission Control to some upcoming Oracle JDK) Argus JMX Browser MC4J JMX Console eclipse-jmx jManage JMiniX hawtio

I am facing a situation where I do not see some method calls not being recorded by the VisualVM application. Wanted to find out the reason and came across this answer on SO . The third point mentions about a potential issue of the sampling method(which is the only option that I am seeing enabled probably because I am doing remote profiling). It mentions about safe points in code and safe point polling by code itself. What do these terms mean? Aleš The issue of inaccuracy of Java sampling profiler tools and its relation to the safe points is very well discussed in Evaluating the Accuracy of

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

Can someone please explain me the difference between Sleeping , Wait , Park , and Monitor thread states in VisualVM. This is what I have found: Running : thread is still running. Sleeping : thread is sleeping (method yield() was called on the thread object) Wait : thread was blocked by a mutex or a barrier, and is waiting for another thread to release the lock Park : parked threads are suspended until they are given a permit. Unparking a thread is usually done by calling method unpark() on the thread object Monitor : threads are waiting on a condition to become true to resume execution What I

I have setup new Cassandra 3.3 cluster. Then I use jvisualvm to monitor Cassandra read/write latency by using MBean (jmx metric). The result of read/write latency is always stable in all nodes for many weeks whereas read/write request in that cluster have normally movement (heavy or less in some day). As I use jvisualvm to monitor Cassandra 2.0 cluster. The read/write latency have normally behavior. It have movement depending on read/wire requests. I wonder that Why the read/write latency statistics of Cassandra 3.0+ are always stable? And I think it is incorrect result. (I have load tested in

I created a heap dump file with hprof using this command: java -agentlib:hprof -cp "..\..\jars\trove.jar;.\bin" com.mysite.MyApp This successfully created the file "java.hprof.txt" which was about 5MB. I then opened up jvisualvm to view this file, and loaded it in. But visualvm appears to be stuck on the loading screen. The screen below has been up for about 10 minutes now. Did I miss a step? Should I have used different options on the command line with hprof? How can I read this heap dump file? VisualVM supports heap dumps in binary HPROF format. It is easier to use VisualVM to create heap