Operating Systems: i5/OS
Personalize the table of contents and search results
Diagnosing problems (using diagnosis tools)
Various diagnosis tools are provided to help you determine the
source and impact of problems occurring in your application serving environment.
Overview
The purpose of this section is to aid you in understanding why
your enterprise application, application server, or WebSphere Application
Server is not working and to help you resolve the problem. 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
- If deploying or running an application results
in exceptions such as ClassNotFoundException, use the Class Loader Viewer to diagnose problems with class
loaders.
- If you already have an error message and want to quickly look up
its explanation and recommended response, look up the message by expanding
the Messages section
of the Information Center under Reference > Messages.
- For help in knowing where to find error and warning messages, interpreting
messages, and configuring log files, see Working
with message logs.
- Difficult problems can require the use of tracing, which exposes
the low-level flow of control and interactions between components. For help
in understanding and using traces, see Working
with trace.
For help in adding log and trace capability to your own application,
see Configuring Java logging using the administrative console.
For help in using settings or tools to help you diagnose the problem,
see Working with troubleshooting tools.
Some of these tools are bundled with the product, and others are freely
downloadable.
- To learn how to work with Diagnostic Providers,
see Working with Diagnostic Providers..
- To find out how to look up documented problems, common mistakes,
WebSphere Application Server prerequisites, and other problem-determination
information on the WebSphere Application Server public Web site, or to obtain
technical support from IBM, see Obtaining help
from IBM.
- The Troubleshoot IBM Developer Kit for Java 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.
- For current information available from IBM Support on known problems
and their resolution, see the WebSphere Application Server Product support page. For last minute updates, limitations, and known problems,
refer to the Release notes.
- 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.
}
Troubleshooting class loaders
Diagnosing problems with message logs
CORBA minor codes
Configuring the hang detection policy
Working with trace
Getting IBM Support
Assistant
Diagnosing out-of-memory errors and Java heap memory leaks
Troubleshooting help from IBM
Diagnosing and fixing problems: Resources for learning
Debugging Service details
Configuration problem settings
Showlog commands for Common Base Events
Working with Diagnostic Providers
Related tasks
Adding logging and tracing to your application
Debugging applications
Related information
http://www.ibm.com/servers/eserver/support/iseries/index.html
|