How do I troubleshoot?

Follow these shortcuts to get started quickly with popular tasks.

Designers and developers of applications that run on the application server might find it useful to use Java logging for generating their application logging. This approach has advantages over simply adding System.out.println statements to your code. Add tracing and logging to your applications

For more detailed information on enabling traces by using scripting, see the Troubleshooting with scripting chapter in the Administering applications and their environment PDF book.

[z/OS] WebSphere Application Server includes a number of troubleshooting tools that are designed to help you isolate the source of problems. Many of these tools are designed to generate nformation to be used by IBM Support, and their output might not be understandable by the customer. [z/OS] Choosing and using diagnosis tools and controls on z/OS

In order to debug your application, you must use your application development tool (such as WebSphere Studio Application Developer) to create a Java project or a project with a Java nature. You must then import the program that you want to debug into the project. Debug WebSphere applications during development

A common error in J2EE applications is a hung thread. The hang detection option is turned on by default. You can configure a hang detection policy to accommodate your applications and environment so that potential hangs can be reported, providing earlier detection of failing servers. When a hung thread is detected, the product notifies you so that you can troubleshoot the problem. Detect hung threads

Use an administrative console page to identify and view problems that exist in the current configuration. Detect product configuration file problems

Use trace to obtain detailed information about the execution of product components, including application servers, clients, and other processes in the environment. Set traces and logs with the console

Use trace to obtain detailed information about the execution of product components, including application servers, clients, and other processes in the environment. Set traces and logs with scripting*

WebSphere Application Server can write system messages to several general purpose logs. Work with message logs

You can use High Performance Extensible Logging (HPEL) to help diagnose problems in WebSphere Application Server Using HPEL to troubleshoot applications

The Logging API Specification (or Java logging), which is defined with Java Specification Request (JSR) 47, is the logging toolkit that is provided by the java.util.logging package. Java logging provides a standard logging API for your applications. Using JSR47 for logging

Before applications can log diagnostic information, you need to specify how you want the server to handle log output, and what level of logging you require. Using the administrative console, you can enable or disable a particular log, specify where log files are stored and how many log files are kept, and specify a format for log output. You can also set a log level for each logger. Using JSR47 for logging: Configuring access logs