What is new for troubleshooters

What is new for troubleshooters

This topic highlights what is new or changed in v6.x for users who are going to use the troubleshooting tools and serviceability features.
The biggest change in troubleshooting support and serviceability is increased ability to automatically detect and recover from problems. Many serviceability improvements are described in the IBM Education Assistant presentation:Serviceability enhancements.
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.

New troubleshooting technology on the Support site

MustGather: Read first for all WebSphere Application Server products
Troubleshooting Guide for WebSphere Application Server

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 V5.1.x prefixes to v6.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 WAS 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.
See Logging and tracing with Java logging.

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 WAS 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.
See The Common Base Event in WebSphere Application Server.

Thread names can be included in logs
Thread name has been added to the Advanced log format and Log Analyzer format. 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.

New troubleshooting technology on the Support site	MustGather: Read first for all WebSphere Application Server products Troubleshooting Guide for WebSphere Application Server

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 V5.1.x prefixes to v6.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 WAS 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. See Logging and tracing with Java logging.

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 WAS 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. See The Common Base Event in WebSphere Application Server.

Thread names can be included in logs	Thread name has been added to the Advanced log format and Log Analyzer format. 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.