[Enterprise Extensions only]

Description of a formatted activity log entry

If you use the showlog utility to format an enterprise services' activity log to a file, the first two lines of the output file show the following two fields:

$LANG
The language of the system where showlog command was run, taken from the system's environment.
$CODESET
The codepage of the system where showlog command was run, obtained from the function call "char * nl_langinfo(CODESET)".

You cannot change this information which is generated by showlog.

The remainder of the formatted output contains entries for events recorded in the activity log.

Content of a formatted activity log entry

Each entry in the activity log has the following fields:

ComponentId: number
A numeric value that identifies the component in WebSphere Application Server enterprise services.
ProcessId: number
The process number under which the client or server is running; this is the identifier by which the operating system knows the process.
ThreadId: number
The thread identifier under which the object placed the event in the activity log. This is the thread identifier by which the operating system knows the thread.
FunctionName: name
An internal name for the function that placed the information in the activity log. This may not be very useful for you.
ProbeId: number
This is typically the line number in the source file that has the function that placed the entry in the event log. However, some components use this field as a probe identifier and assign it some other value.
SourceId: number filename
The number identifies the version of code that is running; the second value is the location of the source code file in the library system from which the code was built. This information may not be very useful to you.
Manufacturer: IBM
Product: WebSphere Application Server
Version: number
The version of the product.
SOMProcessType: number
he type of process that placed this event in the activity log:
1
A client process.
2
An ORB daemon.
5
A server process.
ServerName: name
If this is a server process, the name of the server.
ClientHostName: hostname
The host name of the client associated with the event, if security is enabled for the server process.
ClientUserId: userid
The user ID of the client associated with the event, if security is enabled for the server process.
TimeStamp: yyyy-mm-dd hh:mm:ss.nnnnnnnnn
The date and time when the event was placed in the activity log, in the format: yyyy-mm-dd hh:mm:ss.nnnnnnnnn, where:
yyyy-mm-dd
The date of the event, as a numeric form of year, month, and day (ISO 8601 standard format); for example, 2001-08-15 for the 15th August 2001.
hh:mm:ss.nnnnnnnnn
The time of the event, as a numeric form of hour, minute, and second; for example, 19:45:01.149182980.
UnitOfWork: nnnnn:hhhhh
The unit-of-work identifier for the original request, in the format, nnnnn:hhhhh, where:
nnnnn
A random number.
hhhhh
The name of the host where the original request originated.

If a request is forwarded to another server as part of the original request, the unit of work from the original request is used. This enables clients to track the work that is done as part of an original request.

Note: You may find the UnitOfWork information useful when you are trying to find related entries in the activity log or when you are debugging problems across multiple machines. For more information about how to view activity log entries in UnitOfWork sequence, see Reading the activity log.
Severity: number
The severity of the problem. The possible values are:
1
Error - Indicates there is a problem with the operation that caused the message, and the operation has failed. In this case, see other messages in the log with the same UnitOfWork for additional information.
2
Warning - Indicates there may be a problem with the operation that caused this message. The operation continues and may or may not be successful. In this case, see other messages in the log with the same UnitOfWork for additional information.
3
Informational - The message is informational only. The operation that caused this message continues. In this case, see other messages in the log with the same UnitOfWork for additional information.
Category: number
The category of the failure.

For messages generated from C++, the possible values are:

1
Error - Indicates that a severe error has occurred. These messages are written to the error log, activity log and the Windows platforms event log, which can be viewed using Windows Event Viewer.
2
Activity - Indicates some general form of activity. These messages have one of the three Severity settings and are written to the activity log.
3
Trace - Is used for component trace. These messages are written to trace logs.
4
Trace Data - Is used for additional data for component trace. These messages are written to trace logs.
5
Performance - Is used for performance trace data. These messages are written to trace logs.

For messages generated from C++, the possible values are:

AUDIT
An informational message, written to the activity log.
WARNING
A serious warning message, written to the activity log.
ERROR
A severe error, written to the error log, activity log, and the Windows platforms event log, which can be viewed using Windows Event Viewer.
EVENT, ENTRY, EXIT, DEBUG
Trace messages, written to the trace log.

FormatWarning: number
A non-zero numeric value when an attempt to place the replacement text in the Primary or Extended Message was not correct.
PrimaryMessage:
In the case that the entry was placed in the activity log as part of an exception, the PrimaryMessage field contains the objectName::methodName(parameter list):lineNumber and the type of the exception (this should always be CORBA::exception) and the specific exception that was raised.

This field contains essential information for problem determination and indicates one of the following:

Throw of exception
The entry indicates that the listed function determined that an exception should be thrown. Look at the ExtendedMessage information to help you identify the cause of the problem. This is a category 1 (Error) entry.
Reraised exception
The entry indicates that an exception was received and reraised. This entry allows you to trace related entries in the activity log. This is a category 1 (Error) entry.
Mapping of exception
The entry shows the exception that was received and the new exception that was raised. This is useful when tracking a specific exception through the activity log. This is a category 1 (Error) entry.
Activity entry
An activity entry provides information. If the entry appears during an exception path, it contains information to help determine the cause of the problem for which the exception is being raised. If the entry is not on an exception path, the entry provides information as to the state of the server. This is a category 2 (Activity) entry.

Note: If you see a minor code of this format, 0x49420xxx, where xxx are hexadecimal numbers, see CORBA system exception minor codes for more information about the message.
ExtendedMessage:
The extended message often provides additional information to pinpoint the exact cause of the failure.
RawDataLen:
When raw data is provided as part of this log entry, the length of the raw data is shown in hexadecimal format. The raw data follows this entry and is shown in a 16-byte dump with the ASCII format of the data at the right of the dump.

If the ORB communications trace is turned on, the trace data from GIOP packets is displayed in the RawData field.