Java postmortem diagnostics, Part 1, Introduction to JSR 326 and Apache Kato

Learn how the Apache Kato project can help you analyse the causes of JVM failure

From the developerWorks archives

Adam Pilkington

Date archived: December 19, 2016 | First published: May 05, 2009

The artifacts produced when your Java™ application fails can help you analyse the root causes of the failure. A standard API to facilitate postmortem analysis is being developed by the Java Community process, and the Apache Kato project is under way to produce a reference implementation and tools for this API. This article, the first in a two-part series, introduces the Post mortem JVM Diagnostics API (JSR 326) and summarises the ways Kato will help you make good use of it. Part 2 will explore postmortem-diagnosis scenarios in greater depth.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.

Zone=Java development, Open source
ArticleTitle=Java postmortem diagnostics, Part 1: Introduction to JSR 326 and Apache Kato