Messages

This reference information provides additional information about messages we might encounter while using the product. It is organized according to the identifier of the product feature that produces the message.

Messages are subject to change in service and version upgrades. As far as practically possible, the product will be consistent in the message IDs that are output at particular points of operation. If create automation scripts that involve messages, use the message ID rather than the message text. For example, to detect when an application has started, we can use the following regular expression to get the notification:

"CWWKZ0001I:.*" + appName

WebSphere Application Server system messages originate from a variety of sources, including Application Server components and applications. The message identifier can be either 9 or 10 characters in length and has the form:

CCCC1234X

or

CCCCC1234X

where:

CCCC or CCCCC

is a 4 or 5-character alphabetic component or application identifier.

1234

is a 4-character numeric identifier used to identify the specific message for that component.

X

is an optional alphabetic severity indicator. (I=Informational, W=Warning, E=Error)

Subtopics

• Class loading exceptions
  
• CORBA minor codes
  Applications that use CORBA services generate minor codes to indicate the underlying cause of a failure. These codes are written to the exception stack. Look for "minor code" in the exception stack to locate these exceptions.
• Diagnostic alerts
  In WAS v9.0 the Performance and Diagnostic Advisors are extended to provide more diagnostic alerts to help common troubleshoot problems.
• JMS report messages
  JMS applications can use report messages as a form of managed request/response processing, to give remote feedback to producers on the outcome of their send operations and the fate of their messages.

Converting log files to use IBM unique Message IDs

Diagnose problems (using diagnosis tools)

Change the message IDs used in log files