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

How do I troubleshoot?

Legend for "How do I?..." links

Documentation

Show me

Tell me

Guide me

Teach me

Refer to the detailed steps and reference Watch a brief multimedia demonstration View the presentation for an overview Be led through the console pages Perform the tutorial with sample code
Approximate time: Varies Approximate time: 3 to 5 minutes Approximate time: 10 minutes+ Approximate time: 1/2 hour+ Approximate time: 1 hour+

 

--------------------------------------------------------------------------

Check mark Set traces, logs, and other controls

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

Documentation Documentation link

Show me

Show me demonstration link

Tell me

Documentation link

 

Blank

 

Blank

--------------------------------------------------------------------------

Check mark Work with message logs

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

Documentation

Documentation link

Show me

Show me demonstration link

 

Blank

 

Blank

 

Blank

--------------------------------------------------------------------------

Check mark Detect hung threads

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.

Documentation

Documentation link

 

Blank

 

Blank

 

Blank

 

Blank

--------------------------------------------------------------------------

Check mark Detect product configuration file problems

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

Documentation

Documentation link

 

Blank

 

Blank

 

Blank

 

Blank

--------------------------------------------------------------------------

Check mark Troubleshoot problems that occur during a task

Troubleshoot problems that crop up during a main task such as migrating, installing, administering, securing, or deploying applications.

Documentation

Documentation link

 

Blank

 

Blank

 

Blank

 

Blank

--------------------------------------------------------------------------

Check mark Troubleshoot particular WebSphere application problems

Expand Troubleshooting > Troubleshooting WebSphere applications in the information center table of contents for information about troubleshooting specific application components and their administrative configurations (such as EJB container settings).

--------------------------------------------------------------------------

Check mark Debug WebSphere applications during development

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.

Documentation

Documentation link

 

Blank

 

Blank

 

Blank

 

Blank

--------------------------------------------------------------------------

Check mark Add tracing and logging to your applications

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.

Documentation

Documentation link

 

Blank

 

Blank

 

Blank

 

Blank

--------------------------------------------------------------------------

Check mark Collect troubleshooting details for IBM Support

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 information to be used by IBM Support, and their output might not be understandable by the customer.

Documentation

Documentation link

 

Blank

 

Blank

 

Blank

 

Blank

--------------------------------------------------------------------------

Check mark Using JSR47 for logging

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.

Documentation

Documentation link

 

Blank

 

Blank

 

Blank

 

Blank

--------------------------------------------------------------------------

Check mark Using JSR47 for logging: Writing a handler

There may be occasions when you only want to propagate log records to your own log handlers, rather than participate in integrated logging; in other words, to use a stand alone log handler.

Documentation

Documentation link

 

Blank

 

Blank

 

Blank

 

Blank

--------------------------------------------------------------------------

Check mark Using JSR47 for logging: Writing a formatter

A formatter formats events according to type. Handlers are associated with one or more formatters.

Documentation

Documentation link

 

Blank

 

Blank

 

Blank

 

Blank

--------------------------------------------------------------------------

Check mark Using JSR47 for logging: Writing a filter

A Filter provides optional, secondary control over what is logged, beyond the control provided by the level.

Documentation

Documentation link

 

Blank

 

Blank

 

Blank

 

Blank

--------------------------------------------------------------------------

Check mark Using JSR47 for logging: Configuring access logs

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.

Documentation

Documentation link

 

Blank

 

Blank

 

Blank

 

Blank

--------------------------------------------------------------------------

Check markUsing Common Base Events for logging

WebSphere Application Server uses Common Base Events within its logging framework. Common Base Events can be created explicitly and logged via the Java logging API, or can be created implicitly by using the Java logging API directly. For Common Base Event creation, the application server environment provides a Common Base Event factory with a Content Handler that provides both runtime data and template data for Common Base Events.

Documentation

Documentation link

 

Blank

 

Blank

 

Blank

 

Blank

--------------------------------------------------------------------------

Check mark Creating Common Base Events

In cases where the events generated by the Java logging API are insufficient to describe the event that needs to be captured, Common Base Events can be created using the Common Base Event factory APIs. When you create a Common Base Event you can add data to the Common Base Event before it is logged. WebSphere Application Server is configured to use an event factory that automatically populates WebSphere Application Server specific information into the Common Base Events that it generates.

Documentation

Documentation link

 

Blank

 

Blank

 

Blank

 

Blank

--------------------------------------------------------------------------




Related concepts
Overview and new features for troubleshooting
welc6productov.html

Concept topic    

Terms of Use | Feedback

Last updated: Jun 8, 2005 12:45:23 PM EDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/welc_howdoi_ttrb.html

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