Introduction to Oracle JRockit Mission Control

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Overview of Oracle JRockit 1.0

The Oracle JRockit Mission Control 1.0 tools suite was introduced with Oracle JRockit JDK R26.0.0. These tools are run as standalone tools to the JRockit JVM.

This section contains information on the following subjects:

 


Architectural Overview of JRockit Mission Control 1.0

JRockit Mission Control is available on Oracle JRockit JDK 1.4.2 (R26.2 and later) and JRockit JVM 5.0 (R26.0 and later), see Figure 1-1. The difference between the two is the connection agent used by the JRockit Management Console and the JRockit Management Console user interface itself.

The RMP Agent (JRockit JDK 1.4.2) provides access, among other things, to live data about memory and CPU usage. With the addition of the JMX Agent (available with JRockit JDK 5.0) you will also get access to MBeans available to the platform MBean server. From these MBeans, you can read attributes information, such as garbage collection pauses.

When a JRA recording is started, for example, from the Management Console, it records the status of the JRockit JVM process for the time that you have specified. When the recording is completed, the information is saved to an XML file. This XML file can be viewed and analyzed in the JRockit Runtime Analyzer tool. Typical information that is recorded during a JRA recording is Java heap distribution, garbage collections, and method optimizations.

To find memory leaks in your Java application, you connect the JRockit Memory Leak Detector to the running JRockit JVM process. The Memory Leak Detector connects to the JMX (RMP) Agent that instructs to start a Memory Leak server where all further communication takes place.

Figure 1-1 Architectural Overview of JRockit Mission Control 1.0

Architectural Overview of JRockit Mission Control 1.0

 


The JRockit Management Console

The JRockit Management Console is used to monitor and manage multiple (or single) JRockit JVM instances. It captures and presents live data about memory, CPU usage, and other runtime metrics. For the Management Console that is running on JRockit JDK 5.0, information from any JMX MBean deployed in the JRockit JVM internal MBean server (JMX Agent in Figure 1-1) can be displayed as well. JVM management includes dynamic control over CPU affinity, garbage collection strategy, memory pool sizes, and more.

 


The JRockit Runtime Analyzer (JRA)

The JRockit Runtime Analyzer (JRA) is an on-demand “flight recorder” that produces detailed recordings about the JVM and the application it is running. The recorded profile can later be analyzed off line, using the JRA tool. Recorded data includes profiling of methods and locks, as well as garbage collection statistics, optimization decisions, and object statistics.

 


The JRockit Memory Leak Detector

The JRockit Memory Leak Detector is a tool for discovering, and finding the cause for memory leaks in a Java application. The JRockit Memory Leak Detector’s trend analyzer discovers slow leaks, it shows detailed heap statistics (including referring types and instances to leaking objects), allocation sites, and it provides a quick drill down to the cause of the memory leak. The Memory Leak Detector uses advanced graphical presentation techniques to make it easier to navigate and understand the sometimes complex information.


  Back to Top       Previous  Next