Getting started with run-time problem determination

The run-time problem determination "Getting started" section provides the basic steps for collecting profiling data. It includes instructions for selecting the profiling set that collects the kind of data you need, and provides high-level information about accessing and using the views that can help you with your analysis.

The profiling and logging views are able to pinpoint the following problems, all of which are possible reasons for poor run-time performance:

There are also views to help you locate gaps in code coverage during your profiling runs.

Profiling and logging also includes Probekit, which provides a framework for writing Java code fragments to investigate specific run-time problems.

The "Getting started" section includes the following topics:

Getting started: Creating a profiling configuration for run-time problem determination
A profiling configuration controls data collection during profiling. Create a profiling configuration using the Profile dialog box in the Profiling and Logging perspective.

Getting started: Memory leak analysis
Memory leaks, which in Java often result when objects hold on to references inappropriately, can degrade performance and eventually cause a program to crash. The Profiling and Logging perspective includes views for analyzing your application's memory usage and detecting these leaks.

Getting started: Performance bottleneck detection
Performance bottlenecks are places in your application that prevent the application from running as fast as it should. The Profiling and Logging perspective includes views for examining performance and detecting bottlenecks.

Getting started: Thread bottleneck detection
Thread bottlenecks such as contentions and deadlocks can slow your application or bring it to a halt. The Profiling and Logging perspective includes views and tools that help you detect and resolve these thread problems.

Getting started: Code coverage monitoring
The Profiling and Logging perspective includes views for identifying untested lines and untested methods in your code. When you profile a run to analyze performance or thread bottlenecks, you can also monitor coverage to ensure that you have exercised all the appropriate parts of your application.

Getting started: Probekit for customized profiling
Probekit helps you design and implement probes, which are Java code fragments for monitoring specific characteristics of an application’s run-time behavior. They provide you a means to investigate whatever run-time characteristics interest you.

Getting started: Profiling J2EE applications
Profiling J2EE applications is similar to profiling Java applications, as described in the "Getting started" topics, but there are small differences, and perform special preliminary operations before you start.

 

Parent topic

Detecting and analyzing run-time problems