+

Search Tips   |   Advanced Search

Change the message IDs used in log files


We can change the default format for message IDs in server logs by setting the com.ibm.websphere.logging.messageId.version system property.

Deprecated feature: Beginning with WAS V6.0, logging files are formatted according to a standardized system. However, the default runtime behavior is still configured to use the older format. In new releases of WAS, the message IDs that are written to log files will be changed to ensure they do not conflict with other IBM products.

The default runtime behavior is still configured to use the older message IDs, deprecated in V7.0.

As a result of the default runtime behavior, we might see a mixture of messages that use 4–letter message prefixes and 5–letter message prefixes. The information in this topic explains how to change the configuration so that the messages consistently show with 5–letter message prefixes. The default behavior has not changed to minimize the impact on customers that depend on the existence of the 4–letter message prefixes. depfeat

The following is a sample of an entry in a trace.log file using a default message ID. Note that the message ID is PMON0001A

[1/26/05 10:17:12:529 EST] 0000000a PMIImpl A PMON0001A: PMI is enabled

A sample of the same entry using a new message ID follows. Note that the message ID is CWPMI0001A. All new WAS message IDs begin with 'CW'.

[1/26/05 10:17:12:529 EST] 0000000a PMIImpl A CWPMI0001A: PMI is enabled.

For a logging tool that uses the standardized format, we might want to change the default settings to format the logging output appropriately. You will need to change the configuration for each JVM in the cell if we want the output formatting to be the same across application servers.

 

 

Results

Message IDs written to log files will now be compliant with the new standard.


Converting log files to use IBM unique Message IDs
convertlog
MessageConverter class