Skip Headers
Previous
Previous
 

Frequently Asked Questions

The following issues sometimes arise:

Issue 1   I cannot connect to the JVM. What could be the problem?

Consider the following:

Issue 2   When attempting to connect to a JVM, I get a stack trace indicating that the JVM attempts to communicate with a strange IP or host name. What does this mean?

Sometimes RMI can have a problem determining which address to use. This can happen because of any of the following:

If all else fails, you can try specifying the java.rmi.server.hostname system property. Note that this can affect applications running on the JVM.

Issue 3   I am getting exceptions during startup about classes not being found. What is wrong?

Ensure that you are using JAVA_HOME/bin/jmc to start the JMC client.

Issue 4   Why does Java Mission Control fail to find any local JVMs?

Consider the following:

Issue 5   How do I connect to JBoss?

Before starting JMC, you need to add the -Xbootclasspath/a option to the -vmargs section of the jmc.ini file. The value for this option (after a colon) should be set to the extended classpath that is generated by JBoss's jconsole.bat file (for this, add @echo on to the file and run it).