bea.com | products | dev2dev | support | askBEA |
|
e-docs > WebLogic Server > Administration Console Online Help > Security |
Administration Console Online Help |
Tasks Related Topics Attributes
The Server—>Logging—>Server tab configures a server's local message log. Use this tab to specify the name of the log file and any log file rotation criteria.
In addition, you can use this tab to specify the types of messages that the server sends to standard out.
The server message log does not contain HTTP requests, JDBC messages, or JTA transaction messages. Instead, you can configure separate log files for those requests and messages.
In addition to maintaining its local message log, by default, each server forwards all messages of severity ERROR and higher to the domain log.
If you create applications to run on WebLogic Server, you can configure your applications to generate messages of severity DEBUG. These messages are never forwarded to the domain log and are intended to contain detailed information about the operation of an application or the server.
Changing the Name and Location of the Server Log File
Specifying Which Messages a Server Sends to Standard Out
Specifying the Messages that a Server Forwards to the Domain Log
Overview of WebLogic Server Log Messages and Log Files
The name of the file that stores current log messages. If the pathname is not absolute, the path is relative to the server's root directory. For more information, refer to "A Server's Root Directory." If the name does not include a path element, then pathname is./SERVER_NAME If neither file name nor pathname is specified, then the name is./SERVER_NAME/SERVER_NAME.log If you enable the server to rotate messages across multiple files, this value is the base name for the files that store old messages: FileNamen. |
||
Enables the server to send messages to standard out in addition to the log file. Use StdoutDebugEnabled and StdoutSeverityLevel to determine the type of messages that the server sends to standard out. |
||
Determines whether the server sends messages of the DEBUG severity to standard out in addition to the log file. You must enable Log to Standard Out for this property to be relevant. |
||
The minimum severity of a message that the server sends to standard out. You must enable Log to Standard Out for this value to be relevant. The ascending order of severities is as follows:
|
||
Criteria for moving old log messages to a separate file:
After the server renames a file, subsequent messages accumulate in a new file with the name that you specified in FileName. |
||
The size (1 - 65535 kilobytes) that triggers the server to move log messages to a separate file. After the log file reaches the specified minimum size, the next time the server checks the file size, it will rename the current log file as FileName.n and create a new one to store subsequent messages. (This field is relevant only if you set Rotation Type to By Size.) |
||
Determines the start time (hour and minute) for a time-based rotation sequence. At the time that this value specifies, the server renames the current log file as FileName.n. Thereafter, the server renames the log file at an interval that you specify in FileTimeSpan. Use the following format: hh:mm, where hh is the hour in a 24-hour format and mm is the minute. If the time that you specify has already past, then the server starts its file rotation immediately. |
||
The interval (in hours) at which the server saves old log messages to another file. This value is relevant only you use the time-based rotation type. |
||
Determines whether the server returns stack traces for RMI calls that generate exceptions. With this attribute enabled, if a client issues an RMI call to a server subsystem or to a module running within the server, and if the subsystem or module generates an exception that includes a stack trace, the server will return the exception as well as the stack trace. With this attribute disabled, the server will return exception without the stack trace details. |