Technical data

Message Attributes

Administration Guide 6-7

The following is an example of a log message:

####<Jun 2, 2000 10:23:02 AM PDT> <Info> <SSL> <bigbox> <myServer>

In this example, the message attributes are: Timestamp, Severity, Subsystem, Machine

Name, Server Name, Thread ID, User ID, Transaction ID, Message ID, and Message

Text.

Note: Log messages logged by clients do not have the attributes Server Name or

Thread ID.

Note: The character encoding used in writing the log files is the default character

encoding of the host system.

Message Attributes

Each log message saved in a server log file the attributes listed in the following table

may be defined. The Message Id may also associate the message with additional

attributes (such as Probable Cause and Recommended Action) contained in the

Message Catalog.

Attribute Description

Timestamp The time and date when the message originated, in a format that

is specific to the locale.

Severity Indicates the degree of impact or seriousness of the event reported

by the message. See Message Severity.

Subsystem This attribute denotes the particular subsystem of WebLogic

Server that was the source of the message. For example, EJB,

RMI, JMS.

Server Name

Machine Name

Thread ID

Transaction ID

These four attributes identify the origins of the message.

Transaction ID is present only for messages logged within the

context of a transaction. Note: Server Name and Thread ID are

not present in log messages generated by a Java client and logged

to a client log.