Changing Your JVM

While the JDK Mission Control client can work with many different JVMs, it is highly recommended that you use the Oracle JDK/JVM as your JVM when running the JDK Mission Control Client on the Eclipse platform. Make sure to use Oracle HotSpot JDK 7 Update 14 or later. Running on a JRE is not recommended, as this will disable the autodetection of local JVMs.

To change the JVM on which you run Eclipse:

Go to your file system browser (for example, Windows Explorer).
Locate your Eclipse installation folder (for example, C:\Program Files\Eclipse) and, with a file editor other than Notepad, open the file eclipse.ini. It will look similar as in the following example:

-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256M
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx512m
Make the following changes to the eclipse.ini file:
- Remove all flags related to other JVMs than the JVM (for example, --launcher.XXMaxPermSize 256M).
- On the third line down (after org.eclipse.platform), add the following:
  
  -vm <Full path JAVA_HOME/jre/bin/ folder>
  
  The full path might look like this on Windows:
  
  C:\Program Files\Java\jdk1.7.0\jre\bin\
  
  Or, the path might look like this on Linux and Solaris:
  
  $HOME/jdk1.7.0/jre/bin/
- Depending upon your particular JVM implementation and the applications running on it, you can set any valid JVM command-line option.
  
  For more information on the available command-line options, see Java Command-Line Reference at
  https://docs.oracle.com/javase/7/docs/technotes/tools/solaris/java.html (Solaris, Linux)
  https://docs.oracle.com/javase/7/docs/technotes/tools/windows/java.html (Windows)
When you have finished making the necessary changes to the eclipse.ini file, save and close the file. The following example shows the eclipse.ini file updated to make the JVM the active JVM in a Windows implementation.

-showsplash
org.eclipse.platform
-vm
C:\Program Files\Java\jdk1.7.0\bin\javaw.exe
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms256m
-Xmx512m