Oracle JRockit MissionControl Part 1

There are several tools on the market for performance management. There is  for instance JConsole, the Enterprise Manager ( GridControl) but another nice tool to see how your JVM is doing is JRockit Mission Control, coming with the BEA JRockit JDK

Start and looking at the dashboard gives me already a smile on my face; I feel like I’m in the a real cockpit flying on MBeans an drilldown memory leaks 🙂

Oracle JRockit MissionControl Part 1 jrmc1t

Before we start using Mission Control, we have to do some simple steps to set it up right.

We download the package for our 64 bit Linux WebLogic server, available on To connect from our local desktop, we need a windows client

All binary packages, with the extension *.bin are self-extractable,  we only have to make executable by performing chmod +x  jrockit-jdk1.6.0_20-R28.1.0-4.0.1-linux-x64.bin.

When installation is done, you could run the MissionControl locally, by exporting the display of the WebLogic Linux server to you own desktop, or install a local MissionControl client on your desktop and connect to the remote WebLogic JVM

When starting JRMC, the following screen appears:

Oracle JRockit MissionControl Part 1 jrmc2

Inhere you can create your connections to you WebLogic JVM’s. When connecting remote, you should add the follwing startparameters for you JVM:

JAVA_OPTIONS=”-Djava.rmi.server.hostname=<WebLogic Server>  -Xmanagement:ssl=false,authenticate=false,autodiscovery=true,port=7090″
The port 7090 should be accessible form your own client
Another useful option could be -XX:FlightRecorderOptions=defaultrecording=true.

There are several components to be found in JMRC like:

– JRockit Browser: Browse several  JRockit JVM instances and start monitoring through the Management Console or the Memory Leak Detector.

– Historical Data: For trendwatching; historical data is stored to get an overview over a longer amount of time

– JRockit Runtime Analyzer: to analyze recorded data with JRockit FlightRecorder

Don’t forget to enable use of your platform MBean, in the WebLogic Admin Console

– Memory Leak Detector: detect memory leaks within your application.

– Management Console:  to monitor live data from the JRockit JVM. This tool allows you to monitor the running Java application, create triggers that notify you when condition is met and mail notifications

There are 2 more things to get JRMC working with your WebLogic Server

1. Do not forget to enable the Platform MBean and use of it in your WebLogic Admin Console. You can set it here:

Oracle JRockit MissionControl Part 1 jrmc3

2. Change the diagnostic volume form your WLDF  to “High”  in Environment – ->configuration –> general.

Oracle JRockit MissionControl Part 1 jrmc4

This is the setup part. Next time I will dive deeper into the different options of JRMC. Have fun!!