WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Diagnosing problems (using diagnosis tools)

Why and when to perform this task

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 un-optimized performance, problem determination focuses on finding solutions to functional problems.

Steps for this task

  1. For tips on investigating common problems organized according to tasks within WebSphere Application server, see Troubleshooting by task.
  2. For tips on how to investigate common kinds of problems based on the component that is causing the problem, see Troubleshooting by component.
  3. [Version 6.0.2]If deploying or running an application results in exceptions such as ClassNotFoundException, use the Class Loader Viewer to diagnose problems with class loaders.
  4. If you already have an error message and want to quickly look up its explanation and recommended response, look up the message by selecting the Reference view of the Information Center navigation and expanding Messages.
  5. For help in knowing where to find error and warning messages, interpreting messages, and configuring log files, see Working with message logs.
  6. 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.
  7. For help in adding log and trace capability to your own application, see Log and trace with Java logging.
  8. 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.
  9. 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.
  10. The 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. You can find the guide at http://www.ibm.com/developerworks/java/jdk/diagnosis/.
  11. For current information available from IBM Support on known problems and their resolution, see the IBM Support page. For last minute updates, limitations, and known problems, refer to the Release notes.
  12. 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.



Sub-topics
[Version 6.0.2]Troubleshooting class loaders
Diagnosing problems with message logs
Message reference
CORBA minor codes
Configuring the hang detection policy
Working with trace
Working with troubleshooting tools
Getting IBM® Support Assistant
Troubleshooting help from IBM
Diagnosing and fixing problems: Resources for learning
Debugging Service details
Configuration problem settings
Showlog commands for Common Base Events

Related tasks
Troubleshooting by task
Troubleshooting by component
Add logging and tracing to your application
Debugging applications

Related information
http://www-1.ibm.com/servers/eserver/support/iseries/index.html

Task topic    

Terms of Use | Feedback

Last updated: Dec 11, 2005 4:07:15 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/ttrb_diagfix.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)