About Logging

Logging is the process by which Enterprise Server captures data about events that occur during Enterprise Server operation. This data is recorded in a log file and is usually the first source of information when Enterprise Server problems occur.

Although application components can use the Apache Commons Logging Library to record messages, the platform standard JSR 047 API is recommended for better log configuration.

The following topics are addressed here:

• Log File

• Configuration File

• Logger Namespaces

Log File

Enterprise Server log records are captured in the server.log file, typically located in domain-dir/logs. You can change the default name or location of the log file by following instructions in To Change the Log File Name or Directory.

Enterprise Server log records follow a uniform format:

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

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

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

• yyyy-mm-ddThh:mm:ss.SSSS-Z specifies the date and time that the record was created. For example: 2006-10-21T13:25:53.852-0400

• Log Level specifies the desired log level. You can select any of the following values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, and FINEST. The default is INFO.

• ProductName-Version refers to the current version of the Enterprise Server. For example: glassfish

• LoggerName is a hierarchical logger namespace that identifies the source of the log module. For example: javax.enterprise.system.core

• Key Value Pairs refers to pairs of key names and values, typically a thread ID. For example: _ThreadID=14;

• Message is the text of the log message. For all Enterprise Server SEVERE and WARNING messages and for many INFO messages, the message begins with a message ID that consists of a module code and a numerical value. For example: CORE5004

An example log record might look like this:

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

Configuration File

You can configure logging by editing the logging.properties file. The default logging.properties file is located in the same directory as the domain.xml file, typically domain-dir/config. You can choose a different file name by using the java.util.logging.config.file system property to specify a file name. For example:

 java -Djava.util.logging.config.file=myfile

Logger Namespaces

A logger is provided for each Enterprise Server module. The following table lists the names of the modules and the namespace for each logger.