Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to connect to JConsole on a server running: java version "1.6.0_0" OpenJDK Runtime Environment (IcedTea6 1.4.1) (6b14-1.4.1-0ubuntu12) OpenJDK 64-Bit Server VM (build 14.0-b08, mixed mode)

When I connect using the "Local Process" method, all the tabs are enabled -- when I connect via the "Remote Process" method, it connects just fine, but the only tab that is enabled is the MBeans tab.

share|improve this question

Normally, the local process method will connect you to the JVM's platform MBeanServer, which is where all the management MXBeans are registered that supply all the data for those other tabs. However, when you connect remotely (and this varies by application/application server), may applications tend to spin up one or more of their own MBeanServers which do not have the management MXBeans registered. Consequently, JConsole cannot render those tabs because it does not see the MXBeans required to do so.

If you see a bunch of application server specific MBeans in JConsole when you connect remotely (like jboss, or weblogic) then that's what's going on.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.