Comments on: JConsole: analyze your Java apps

By: Jiri Sedlacek

Jiri Sedlacek — Fri, 09 Oct 2009 21:30:39 +0000

A minor correction – JConsole is part of JDK since 5.0. JConsole is a great tool which provides almost everything related to MBeans.

VisualVM has a richer feature set since it utilizes more technologies to get the data: JMX, jvmstat, Attach API and Serviceability Agent. Some features are available in both tools (taking thread dumps, heap dumps etc. – but it’s more user-friendly in VisualVM) and some just in VisualVM (like profiling). I believe VisualVM will do a better job for a Java developer.

By: CertPal

CertPal — Fri, 09 Oct 2009 07:04:58 +0000

Follow this up with an article on VisualVM. It integrates well with eclipse. I was planning on writing an article about it too.

By: Veera

Veera — Thu, 08 Oct 2009 17:18:31 +0000

agree with the other people who commented. VisualVM is the better alternative.

By: Kiev Gama

Kiev Gama — Thu, 08 Oct 2009 16:26:30 +0000

You should definitely take a look at the JVisualVM (https://visualvm.dev.java.net/). It supersedes JConsole.
@PhiLho, you can access MBeans from the VisualVM since you are able to retrieve a JMX connection to your Java application.

By: Use JConsole to analyse your Java apps « Scotsman on a Horse

Use JConsole to analyse your Java apps « Scotsman on a Horse — Thu, 08 Oct 2009 15:49:45 +0000

[...] JavaBlogging » JConsole: analyze your Java apps Today we will show a pretty useful program which is a part of Java JDK but whose existence is not known to many Java programmers. It’s named jconsole and it is a GUI client for accessing Java Management Extensions (JMX). In short, it allows you to view a lot of data about memory usage, running threads, garbage collector performance and much more other useful runtime informations about any Java process running on your machine. Published in: [...]

By: PhiLho

PhiLho — Wed, 07 Oct 2009 12:50:34 +0000

I thought JConsole was outdated by JVisualVM. Are there things JConsole can do that JVisualVM cannot?
Perhaps using these MBeans?

“[MBeans are] kind of Java Beans with getters and setters”
I thought Java Beans always have getters and setters.