Book Image

Oracle JRockit: The Definitive Guide

Book Image

Oracle JRockit: The Definitive Guide

Overview of this book

Oracle JRockit is one of the industry’s highest performing Java Virtual Machines. Java developers are always on the lookout for better ways to analyze application behavior and gain performance. As we all know, this is not as easy as it looks. Welcome to JRockit: The Definitive Guide.This book helps you gain in-depth knowledge of Java from the JVM’s point of view. We will explain how to write code that works well with the JVM to gain performance and scalability. Starting with the inner workings of the JRockit JVM and finishing with a thorough walkthrough of the tools in the JRockit Mission Control suite, this book is for anyone who wants to know more about how the JVM executes your Java application and how to profile for better performance.
Table of Contents (23 chapters)
Oracle JRockit
Credits
Foreword
About the Authors
Acknowledgement
About the Reviewers
Preface
12
Using the JRockit Management APIs
Bibliography
Glossary
AST
CAS
HIR
IR
JFR
JMX
JRA
JSR
LIR
MD5
MIR
PDE
RCP
SWT
TLA
Index

Debugging JRockit Mission Control


JRockit Mission Control can be started in debugging mode to provide more information. Simply add the –debug flag when launching the jrmc executable. Starting in debug mode will cause various subsystems to behave differently. For example, the console charts will start showing rendering information and log levels will be changed to display more verbose output.

To view the log messages sent to the console on Windows systems, stderr must be redirected somewhere. This is because the jrmc launcher is derived from the javaw launcher. Following is an example:

D:\>%JROCKIT_HOME%\bin\jrmc –consoleLog -debug 2>&1 | more

To only change the logging levels, select a Logging settings file in the Preferences. The logging settings file is a file on standard java.util.logging format. After changing the logging settings, JRockit Mission Control must be restarted.

The following example shows the debug settings used when starting with the –debug flag:

##############...