Diagnosis tools

 

+

Search Tips   |   Advanced Search

 

Overview

Unlike performance tuning, which focuses on solving problems associated with slow processes and non-optimized performance, problem determination focuses on finding solutions to functional problems.

 

Procedure

  1. For ClassNotFoundException use the Class Loader Viewer to diagnose problems with class loaders.

  2. If you already have an error message and want to quickly look up its explanation and recommended response, look up the message...

    Reference | Messages

  3. Difficult problems can require the use of tracing, which exposes the low-level flow of control and interactions between components.

  4. Add log and trace capability to your applications

  5. Work with troubleshooting tools.

  6. Work with Diagnostic Providers.

  7. Look up...

  8. The site IBM developer kits: Diagnosis documentation describes debugging techniques and the diagnostic tools that are available to help you solve problems with Java. It also gives guidance on how to submit problems to IBM.

  9. Obtain current information available from IBM Support on known problems and their resolution.

  10. Last minute updates, limitations, and known problems.

  11. IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the Must gather documents page for information to gather to send to IBM Support.



Troubleshoot class loaders
Diagnose problems with message logs
Message reference
CORBA minor codes
Configure the hang detection policy
Work with trace
Work with troubleshooting tools
Get IBM Support Assistant

Diagnose out-of-memory errors and Java heap memory leaks
Troubleshoot help from IBM
Diagnose and fix problems: Resources for learning
Debug Service details
Configuration problem settings
Showlog commands for Common Base Events
Work with Diagnostic Providers

 

Related tasks

Adding logging and tracing to your application
Debugging applications