JRockit, as a Java runtime, is required to constantly monitor the running Java application. As has been explained in previous chapters, JRockit must, among other things, be able to find out in which methods the Java application is spending the most time executing code. JRockit is also responsible for keeping track of the memory usage and memory allocation behavior of the application—it would be fairly upsetting if JRockit forgot a few objects, or if memory was not reclaimed when objects were no longer referenced.

The wealth of data that JRockit already collects is, of course, a very good source of information when profiling your Java program or when doing diagnostics.

In this, the second part of the book, the JRockit tools suite is presented. The following chapters introduce four of the tools that are included in the JRockit distribution—the JRockit Mission Control Console, the JRockit Runtime Analyzer (which was superseded by the JRockit Flight Recorder...