Log files are named according to the component they are logging and the host name where the component runs. For example, a log file for the session director running on hostA is named sd.hostA.log.
The following table lists possible log files and on which hosts they can be found.
The following information is included for all messages recorded at the INFO, WARN, ERROR, and FATAL log levels:
The remainder is the main body of the message. It can include information such as error domain, consumer ID, command, workDir, and hostname, along with the message.
Displays the time when the exception was thrown. The format for the time stamp is:
For Linux/UNIX users only—By default, the time displayed in the logger files is GMT. The format of the timestamp can be changed by editing the related time zone settings in each log4j.properties file in $SOAM_HOME/conf. The properties files contain instructions on how to implement this change.
Displays the log level of the logger that logged the message.
Displays the ID of the Symphony component. The process ID is used to differentiate between daemons when more than one daemon of the same type runs on the host, such as when multiple session managers run on the same host.
The soamview app command displays the process ID of the session manager and soamview task displays the process ID of the service instance. The identity of the process that generated the message can be determined by comparing the process ID in the message with the process IDs displayed by soamview app and soamview task.
Displays the thread of the program that triggered the message.
Displays the name of the logger component used to set the log level of the component that generated the message. The log4j logger components are listed in the properties files. These loggers are used to set the logging levels of specific components such as session director, session manager, service instance manager, repository service, and the CLI.
Displays the error code that uniquely identifies the error. Error codes and their corresponding messages are listed in the Error Message Reference.
Displays the name of the source code file that triggered the message.
Displays the number of the line in the file that triggered the message.
Displays the domain in which the message was triggered. Domains are virtual groups that categorize messages to precisely identify the component the message applies to.