X

Poonam Bajaj's Blog

  • April 2, 2015

Updates to the Java Troubleshooting Guide

Poonam Parhar
Consulting Member of Technical Staff

Mattis Castegren who is my manager at Oracle, and is the guest writer for this blog post would like to share some details on the Java Troubleshooting Guide. Here's what he has to say:--

With the release of JDK 8, the official Java Troubleshooting Guide got a big overhaul. All pages were looked over and updated for JDK 8, and the two previous guides for the JVM and for Desktop Technologies were merged into one.

In
the last month, with the release of 8u40, we have launched the next
phase in this project. In this phase, we have added a lot of chapters
about the new supportability tools that have been introduced in Java
over the last few years.

The biggest new additions are a set of
pages on how to use the Java Flight Recorder (JFR). If you haven't used
JFR before, you should definitely check out the following chapters:

2.3 What are Java Flight Recordings

2.4 How to Produce a Flight Recording

2.5 Inspect a Flight Recording

These
chapters contain step by step instructions on how to record a JFR and
also goes through what to look for in a recording to find common issues.
The chapters contain lots of screen shots and details on how to
interpret the data.

Once you have learned the basics, you can also look at the following two chapters on how to use JFR to debug specific issues:

3.1 Debug a Memory Leak Using Java Flight Recorder

4 Troubleshoot Performance Issues Using JFR

When
you have read through these chapters, you will be ready to use this
great tool to find bottle necks in your own application.

Other new additions to the troubleshooting guide is a new chapter on how to set up Java for better troubleshooting: Prepare Java for Troubleshooting, as well as a lot of minor updates and clarifications.

Join the discussion

Comments ( 1 )
  • guest Wednesday, August 19, 2015

    Is there a PDF version of this guide?


Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.