Log Records

The Communications Server uses the Java EE platform Logging API specified in JSR 047. Communications Server logging messages are recorded in the server log, normally found at domain-dir/logs/server.log. When a log is rotated, Communications Server creates a new, empty file named server.log and renames the old file server.log_date, where date is the date and time when the file was rotated.

The components of the Communications Server generate logging output. Application components can also generate logging output.

Application components may use the Apache Commons Logging Library to log messages. The platform standard JSR 047 API, however, is recommended for better log configuration.

Log records follow a uniform format:

[#|yyyy-mm-ddThh:mm:ss.SSS-Z|Log Level|ProductName-Version|LoggerName|Key Value Pairs|Message|#]

For example:

[#|2006-10-21T13:25:53.852-0400|INFO|sun-appserver9.1|javax.enterprise.
system.core|_ThreadID=13;|CORE5004: Resource Deployed: 
[cr:jms/DurableConnectionFactory].|#]

In this example,

• [# and #] mark the beginning and end of the record.

• The vertical bar (|) separates the record fields.

• 2006-10-21T13:25:53.852-0400 specifies the date and time.

• The Log Level is INFO. This level may have any of the following values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, and FINEST.

• The ProductName-Version is sun-glassfish-comms-server2.0.

• The LoggerName is a hierarchical logger namespace that identifies the source of the log module, in this case javax.enterprise.system.core.

• The Key Value Pairs are key names and values, typically a thread ID such as _ThreadID=14;.

• The Message is the text of the log message. For all Communications Server SEVERE and WARNING messages and many INFO messages, it begins with a message ID that consists of a module code and a numerical value (in this case, CORE5004).

The log record format might be changed or enhanced in future releases.