Diagnosing problems

You can use problem determination to understand why your application, or server is not working.

Why and when to perform this task

The following topic can aid you in understanding why your enterprise application or server is not working, and they can help you resolve problems. 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. For more information about diagnosing problems, see the Diagnosing problems (using diagnosis tools) section in the WebSphere Application Server Network Deployment, Version 6.0, information center.

Steps for this task

  1. Investigate common problems organized according to functional areas within IBM® WebSphere® Process Server in Troubleshooting by function.
  2. If you already have an error message and want to quickly look up its explanation and recommended response, look up the message by selecting Reference in the information center navigation and expanding Messages.
  3. For help in knowing where to find error and warning messages, interpreting messages, and configuring log files, expand the Diagnosing problems (using diagnosis tools) section in the WebSphere Application Server Network Deployment, Version 6.0, information center navigation and select Working with message logs.
  4. 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, expand the Diagnosing problems (using diagnosis tools) section in the WebSphere Application Server Network Deployment, Version 6.0, information center navigation and select Working with trace.
  5. For help in adding log and trace capability to your own application, see Adding logging and tracing to your application.
  6. For help in using settings or tools to help you diagnose the problem, expand Diagnosing problems (using diagnosis tools) section in the WebSphere Application Server Network Deployment, Version 6.0, information center navigation and select Working with troubleshooting tools. Some of these tools are bundled with the product, and others are downloadable.
  7. To find out how to look up documented problems, common mistakes, WebSphere Process Server prerequisites, and other problem-determination information on the WebSphere Process Server public Web site, or to obtain technical support from IBM, see Obtaining help from IBM.
  8. The IBM Developer Kit and Runtime Environment, Java™ 2 Technology Edition, Version 1.4.1 Diagnostics Guide 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 IBM developer kits: Diagnosis documentation Web site.
  9. For current information available from IBM Support on known problems and their resolution, see the IBM Support page.
  10. IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the WebSphere Process Server support page.

Terms of use |

Last updated: Thu Apr 27 15:07:55 2006

(c) Copyright IBM Corporation 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)