Archive for October, 2007

Java diagnostics, IBM style, Part 4: Extending the IBM Diagnostic and Monitoring Tools for Java - Dump Analyzer with analysis modules

In the first article in this series, you learned about the IBM Dump Analyzer for Java, a tool that can perform analysis against a formatted system dump and offer suggestions for problem diagnosis. One of the great advantages of this tool is that you can extend its functionality by writing your own analysis modules. This article wraps up this series on IBM diagnostic tooling for the Java platform by showing you how to build analyzers that will help you plumb the depths of your system dumps and fine-tune your Java code.

The busy Java developer's guide to db4o: Structured objects and collections

Object-oriented applications make considerable use of inheritance, and they frequently want to use that inheritance (or "is-a") relationship to categorize and organize objects within a given system. This can prove difficult in a relational storage scheme, which has no intrinsic concept of inheritance, but in an OODBMS, it's a core feature. In this installment of The busy Java developer's guide to db4o, discover the surprising ease (and power) of using inheritance as a core feature when creating queries in db4o.

Java diagnostics, IBM style, Part 4: Extending the IBM Dump Analyzer for Java with analysis modules

In the first article in this series, you learned about the IBM Dump Analyzer for Java, a tool that can perform analysis against a formatted system dump and offer suggestions for problem diagnosis. One of the great advantages of this tool is that you can extend its functionality by writing your own analysis modules. This article wraps up this series on IBM diagnostic tooling for the Java platform by showing you how to build analyzers that will help you plumb the depths of your system dumps and fine-tune your Java code.

Java diagnostics, IBM style, Part 3: Diagnosing synchronization and locking problems with the Lock Analyzer for Java

The IBM Lock Analyzer for Java, available from alphaWorks, provides real-time lock monitoring on a running Java application. It highlights threads suffering from lock contention that could be hurting application performance. Developers can use this information to modify their applications to reduce lock contention and thus improve performance. This article introduces the IBM Lock Analyzer for Java, explains the architecture on which it is built, and provides some thoughts about the tool's future direction.