 PDF 文書ファイルをダウンロードする (1865 KB)
Chapter 15 Configuring LoggingThis chapter briefly describes how to use the Admin Console to configure logging and view the server log. It contains the following sections: About LoggingLog RecordsThe Application Server uses the Java 2 platform Logging API specified in JSR 047. Application Server logging messages are recorded in the server log, normally found at domain-dir/logs/server.log. The domain-dir/logs directory contains two other kinds of logs in addition to the server log. In the access subdirectory are the HTTP Service access logs, and in the tx subdirectory are the Transaction Service logs. For information about these logs, see To configure the HTTP Service access log and Configuring Transactions. The components of the Application 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: [#|2004-10-21T13:25:53.852-0400|INFO|sun-appserver-e8.1|javax.enterprise. system.core|_ThreadID=13;|CORE5004: Resource Deployed: [cr:jms/DurableConnectionFactory].|#] In this example,
The log record format might be changed or enhanced in future releases. The Logger Namespace HierarchyThe Application Server provides a logger for each of its modules. The following table lists the names of the modules and the namespace for each logger in alphabetical order, as they appear on the Log Levels page of the Admin Console (see To configure log levels). The last three modules in the table do not appear on the Log Levels page. Table 15–1 Application Server Logger Namespaces
Admin Console Tasks for Logging
|
javax.enterprise.resource.corba.ORBId.transport |
Click Save to save the changes, or click Default to restore the default values.
Calls to System.out.println are logged at the INFO level using the logger name javax.enterprise.system.stream.out. Calls to System.err.println are logged at the WARNING level using the logger name javax.enterprise.system.stream.err. To turn off the logs from these sources, specify the logger name with the value OFF in the Additional Properties area.
Changes to the Log Level settings take effect immediately. They are also saved in the domain.xml file for use when the server restarts.
To view the server log
-
In the tree component, expand the node for the server instance whose log you want to view.
-
On the General Information page, click View Log Files.
-
Use the Search Criteria area to customize and filter the log viewer. Use the basic fields as follows:
-
Instance Name — Choose an instance name from the drop-down list to view the log for that server instance. The default is the current server instance.
-
Log File — Choose a log file name from the drop-down list to view the contents of that log. The default is server.log.
-
Timestamp — To view the most recent messages, select Most Recent (the default). To view messages only from a certain period of time, select Specific Range and type a date and time value in the From and To fields that appear. For the Time value, the syntax must take the following form (SSS stands for milliseconds):
hh:mm:ss.SSS
For example:
17:10:00.000
If the From value is later than the To value, an error message appears.
-
Log Level — To filter messages by log level, choose a log level from the drop-down list. By default, the display includes all messages that appear in the server log at the chosen log level and more severe levels. Select the checkbox labeled “Do not include more severe messages” to display messages at only the chosen level.
To ensure that the messages you want to view appear in the server log, first set the appropriate log levels on the Log Levels page. See To configure log levels
If you choose to filter log messages based on log level, only messages matching the specified filter criteria are shown. However, this filtering does not affect which messages are logged to the server log.
The most recent 40 entries in the server log appear, with the settings specified on the Logging Settings and Log Levels pages.
Click the triangle next to the Timestamp header to sort the messages so that the most recent one appears last.
To view a formatted version of any message, click the link marked
(details)
A window labeled Log Entry Detail appears, with a formatted version of the message.
At the end of the list of entries, click the buttons to view earlier or later entries in the log file.
Click Advanced Search in the Search Criteria area to make additional refinements to the log viewer. Use the Advanced Options fields as follows:
-
Logger — To filter by module, choose one or more namespaces from the drop-down list. Use shift-click or control-click to choose multiple namespaces.
Selecting a namespace at a higher level selects all the namespaces below it. For example, selecting javax.enterprise.system also selects the loggers for all the modules under that namespace: javax.enterprise.system.core, javax.enterprise.system.tools.admin, and so on.
-
Custom Logger — To view messages from loggers specific to a particular application, type the logger names in the text field, one per line. If the application has several modules, you can view any or all of them. For example, suppose the application has loggers with the following names:
com.mycompany.myapp.module1 com.mycompany.myapp.module2 com.mycompany.myapp.module3
To view messages from all modules in the application, type com.mycompany.myapp. To view messages from module2 only, type com.mycompany.myapp.module2.
When you specify one or more custom loggers, messages from Application Server modules appear only if you specify them explicitly in the Logger area.
-
Name-Value Pairs — To view output from a specific thread, type the key name and value for that thread in the text field. The key name is _ThreadID. For example:
_ThreadID=13
Suppose that com.mycompany.myapp.module2 runs in several threads. To refine the log viewer to show only the output from a single thread, specify that module’s logger in the Custom Logger field, and then specify the thread ID in this field.
-
Display — To view more than 40 messages at a time (the default), choose another of the available values from the drop-down list (100, 250, or 1000).
To view stack traces, deselect the “Limit excessively long messages” checkbox. By default, stack traces do not appear in the viewer; to view them, click the (details) link for a message.
Click Basic Search to hide the Advanced Options area.
-