This version provides many new features for troubleshooting and servicing the product.
The biggest change in troubleshooting support and
serviceability is increased ability to automatically detect and recover from
problems. The troubleshooting section has been revamped and expanded to include
extensive support information, including the ability to search live, Web-based
support resources by using the customized query fields in the "Web search"
page.
Many serviceability improvements are described in the IBM Education Assistant presentation: Serviceability enhancements.
New troubleshooting technology on the Support site | |
Support assistant | With the IBM Support Assistant, creating and sending an effective
problem report is quicker and easier; and customer self-help is more effective.
It enables you to:
|
Improved message text, new message prefixes | Messages for key product components used during installation, migration, and initial configuration have been improved. Additional components have messages now. Message prefixes have changed. The message reference provides a mapping of Version 5.1.x prefixes to Version 6.0.x prefixes. |
Java logging framework from JSR47 is exploited | In J2SE 1.4, the Java logging framework was introduced via JSR47.
In WebSphere Application Server, messages and trace logged to both JRAS and
JSR47 logging APIs are passed into the JSR47 logging infrastructure. This
allows JSR47 Handlers connected to the root JSR47 Logger to receive all WebSphere
Application Server log content. JSR47 and JRAS Logger levels can be controlled
via the admin console troubleshooting section. WebSphere Application Server
also builds its logs from the JSR47 framework by connecting its Handlers to
the root Logger. The JSR47 Logging infrastructure allows for flexible pluggability of custom Handlers into the logging infrastructure to enable custom logs. By appropriate configuration, the Handlers can receive WebSphere Application Server's logged events, and events logged to Loggers instantiated by your applications. |
![]() |
![]() The WebSphere Application Server support for Jakarta Commons Logging does not change interfaces defined by Jakarta Commons Logging. See Configuring applications to use Jakarta Commons Logging. |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() To help you analyze memory leak problems when memory leak detection occurs, some automated heap dump generation support is available. See Enabling automated heap dump generation. WebSphere Application Server has implemented a lightweight memory leak detection mechanism that runs within the WebSphere Runtime Performance Advisor framework. This mechanism is designed to provide early detection of memory problems in test and production environments. This framework is not designed to provide analysis of the source of the problem, but rather to provide notification and help generating the information that is required to use analysis tools. The mechanism only detects memory leaks in the Java heap and does not detect native leaks. |
![]() |
![]() Restriction: The Class Loader Viewer is not available on
the J9 Java virtual machine, which includes the AMD 64-bit platforms.
|
JRAS is deprecated | The JRAS API is deprecated. Users are directed to use the JSR47 logging infrastructure instead. See Deprecated and removed features for more information about this and other deprecated items. |
Common Base Events describe system situations | Common Base Events are data structures used to describe situations
that occur in the system. Common Base Events are used for various purposes,
including representing things such as business events, configuration events,
error events, and so on. The WebSphere Application Server now uses Common
Base Events as the internal representation of logged messages. Common Base Events are logged via JSR47 and as such can be received and operated on from JSR47 Handlers. Handlers which are not programmed to the Common Base Event specification will also be able to consume these events as CommonBaseEventLogRecords. Handlers which are programmed to the Common Base Event specification can take advantage of fields within the Common Base Events. |
Thread names can be included in logs | Thread name has been added to the Advanced log format and Log Analyzer format. The Log Analyzer format preserves trace information in the text format output of the Showlog tool. Log Analyzer is deprecated in WebSphere Application Server Version 6.1. The advanced log format is available as an output format for the trace log and system out log. The thread name is now included in this format to enable easier correlation with other types of diagnostic data. The log analyzer format is available as an output format for the trace log. The thread name is now included in this format to enable easier correlation with other types of diagnostic data. |