Menu
I read couple of links about JMX and VisualVM, but still have a couple of questions around them.
As per my understanding, JMX & VisualVM are 2 different JVM monitoring tools. In-addition, JMX has APIs, which a java application could incorporate and allow the monitoring tools to better monitor the application.
Could someone clarify if this understanding is correct or flawed ? If flawed, could you please point to any articles explaining this difference/comparison better ?
Also, when do i go for using JMX or VisualVM to monitor my java based web application hosted on a Tomcat 6.1 server ?
983
The JVM software exposed via the JMX connection can now be monitored and managed via Java 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.
Java VisualVM is a tool that provides a visual interface for viewing detailed information about Java applications while they are running on a Java Virtual Machine (JVM), and for troubleshooting and profiling these applications.
Java VisualVM was first bundled with the the Java platform, Standard Edition (Java SE) in JDK version 6, update 7.
That's not correct. JConsole & Java VisualVM are 2 different JVM monitoring tools. Java Management Extensions (JMX) is a Java technology that supplies tools for managing and monitoring applications, like JConsole or Java VisualVM
71
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
