Skip to content

Latest commit

 

History

History
83 lines (59 loc) · 3.5 KB

README.md

File metadata and controls

83 lines (59 loc) · 3.5 KB
Raw

JDK Mission Control Tutorial

This tutorial provides plenty of examples and material to help you learn JDK Mission Control (7+).

Preparations

Since it is not practical to pre-package everything required to run the material here at GitHub, there are some preparations required before starting the Tutorial.

Setting up the JDK

You will need to have a JDK 11 or later to do this tutorial. You can either use the Oracle JDK or any OpenJDK build, for example the one provided by Oracle.

You will need to ensure that java for your JDK is on your path, and you should also make sure that your JAVA_HOME variable is set to the parent folder of the bin folder containing your java binary.

Getting the stand alone version of JMC

There are various binary builds of JMC available. See the JMC github repo for alternatives (any will do): https://github.com/openjdk/jmc#readme

Setting up Eclipse

The tutorial will be easier to run if you have an Eclipse installed. You will need an Eclipse Oxygen 4.8.0 or later. You will also need to add some VM arguments.

For example:

-vmargs
-Djdk.attach.allowAttachSelf=true
--add-exports=java.xml/com.sun.org.apache.xerces.internal.parsers=ALL-UNNAMED
--add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED
--add-exports=java.management/sun.management=ALL-UNNAMED
--add-exports=java.management/sun.management.counter.perf=ALL-UNNAMED
--add-exports=jdk.management.agent/jdk.internal.agent=ALL-UNNAMED
--add-exports=jdk.attach/sun.tools.attach=ALL-UNNAMED
--add-opens=java.base/java.net=ALL-UNNAMED
--add-opens=jdk.attach/sun.tools.attach=ALL-UNNAMED

Depending on your platform you will also need to add one final export.

If running on Windows, also add:

--add-exports=java.desktop/sun.awt.windows=ALL-UNNAMED

If running on Mac OS, also add:

--add-exports=java.desktop/sun.lwawt.macosx=ALL-UNNAMED

If running on Linux, also add:

--add-exports=java.desktop/sun.awt.X11=ALL-UNNAMED

You may also want to ensure that your newly setup JDK is being used for running Eclipse. This can be enforced by using the -vm option in the eclipse.ini file. Don't forget that the -vmargs option must be last in the file. For example:

-vm
/Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home/bin
-vmargs
-Djdk.attach.allowAttachSelf=true
...

Adding the Eclipse plug-ins

Next you will want to add the JMC plug-ins. You can either get the update site pre-built from AdoptOpenJDK (https://adoptopenjdk.net/jmc), or build it yourself. Install git (if you don't already have it) and run the following command in the folder you wish to clone the JMC source:

git clone https://github.com/openjdk/jmc

Follow the instructions in the README.md found in the root of the JMC repository on how to create and access the update sites for Eclipse.

Importing the projects

To import the projects into Eclipse, create a new Workspace and simply import all the projects available in the projects folder.

Running the Tutorial

The tutorial instructions explain in detail how to run the JMC labs. If running the labs from within Eclipse, first ensure that you have set up an Eclipse properly, added the plug-in version of JMC, and imported the projects.

About

This tutorial is for learning how to use JDK Mission Contol. It is provided under GPLv3 as is. If you find a problem, please open a ticket or feel free to provide a pull request.