Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# Server --> Logging --> Server

Tasks Related Topics Attributes

## Overview

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.

### Debug Messages

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.

## Tasks

Viewing Server Logs

Changing the Name and Location of the Server Log File

Specifying Which Messages a Server Sends to Standard Out

Rotating Log Files

Specifying the Messages That a Server Forwards to the Domain Log

Viewing the Domain Log

## Related Topics

Overview of WebLogic Server Log Messages and Log Files

Writing Debug Messages

## Attributes

Table 308-1

Attribute Label | Description | Value Constraints
--- | --- | ---
Server File Name | 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 To include a time or date stamp in the file name when the log file is rotated, add `java.text.SimpleDateFormat` variables. Surround each variable with percentage (`%`) characters. For example, `myserver_%yyyy%_%MM%_%dd%_%hh%_%mm%.log` If you do not include a time and date stamp, the rotated log files are numbered in order of creation `filename` `nnnnn`, where `filename` is the name configured for the log file. MBean: `weblogic.management. configuration.LogMBean` Attribute: `FileName` | Default: weblogic.log Configurable: yes
Log to Stdout | 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. MBean: `weblogic.management. configuration.ServerMBean` Attribute: `StdoutEnabled` | Default: true Valid values: true false Dynamic: yes
Debug to Stdout | 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. MBean: `weblogic.management. configuration.ServerMBean` Attribute: `StdoutDebugEnabled` | Default: false Valid values: true false Dynamic: yes
Stdout Severity Threshold | 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: `INFO(64)`. Used for reporting normal operations. `WARNING(32)`. A suspicious operation or configuration has occurred but it may not have an impact on normal operation. `ERROR(16)`. A user error has occurred. The system or application is able to handle the error with no interruption, and limited degradation, of service. `NOTICE(8)`. An `INFO` or `WARNING`-level message that is particularly important for monitoring the server. Only WebLogic Server subsystems write messages of this severity type. `CRITICAL(4)`. A system or service error has occurred. The system is able to recover but there might be a momentary loss, or permanent degradation, of service. `ALERT(2)`. A particular service is in an unusable state while other parts of the system continue to function. Automatic recovery is not possible; the immediate attention of the administrator is needed to resolve the problem. `EMERGENCY(1)`. The server is in an unusable state. This severity indicates a severe system failure or panic. MBean: `weblogic.management. configuration.ServerMBean` Attribute: `StdoutSeverityLevel` | Default: WARNING Valid values: INFO WARNING ERROR NOTICE CRITICAL ALERT EMERGENCY Dynamic: yes
Rotation Type | Criteria for moving old log messages to a separate file: `None`. Messages accumulate in a single file. You must erase the contents of the file when the size is unwieldy. `By Size`. When the log file reaches the size that you specify in `FileMinSize`, the server renames the file as FileName.n. `By Time`. At each time interval that you specify in `TimeSpan`, the server renames the file as FileName.n. After the server renames a file, subsequent messages accumulate in a new file with the name that you specified in `FileName`. MBean: `weblogic.management. configuration.LogMBean` Attribute: `RotationType` | Default: `By Size` Dynamic: yes
Minimum File Size | 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.) MBean: `weblogic.management. configuration.LogMBean` Attribute: `FileMinSize` | Units: kilobytes Minimum: 1 Maximum: 65535 Default for Development Mode: 500 Default for Production Mode: 5000 Configurable: yes Dynamic: yes
Rotation Time | 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. MBean: `weblogic.management. configuration.LogMBean` Attribute: `RotationTime` | Default: 00:00 (12:00 AM) Configurable: yes Dynamic: yes
File Time Span | 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. MBean: `weblogic.management. configuration.LogMBean` Attribute: `FileTimeSpan` | Units: hours Minimum: 1 Default: 24 Dynamic: yes
Limit Number of Retained Log Files | Specifies whether the number of files that this WebLogic Server creates to store old messages should be limited. After the server reaches this limit, it overwrites the oldest file. MBean: `weblogic.management. configuration.LogMBean` Attribute: `NumberOfFilesLimited` | Default: false
Log Files to Retain | The maximum number of log files that this WebLogic Server creates when it rotates the log. (This field is relevant only if you check the Number of Files Limited box.) MBean: `weblogic.management. configuration.LogMBean` Attribute: `FileCount` | Default: 7
Instrument Stack Traces | Determines whether the server returns stack traces for RMI calls that generate exceptions when interoperating with a client from a release prior to Weblogic 8.1. 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 exceptions without the stack trace details. MBean: `weblogic.management. configuration.ServerMBean` Attribute: `InstrumentStackTraceEnabled` | Default: true Valid values: true false Dynamic: yes