Skip navigation.

WebLogic Server Configuration Reference

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents Index View as PDF   Get Adobe Reader




Configures the location, file-rotation criteria, and number of files that a WebLogic Server uses to store log messages. The methods in this class configure both server and domain log files.



FileMinSize="number of kilobytes"
FileTimeSpan="number of hours"
NumberOfFilesLimited=( "true" | "false" )
RotationType=( "bySize" | "byTime" | "none" )


Parent Elements



Table 45-1 Log attributes



Range of Values and Default


The maximum number of log files that the server creates when it rotates the log. Only valid if isNumberOfFilesLimited is true and setRotationType is either Size or Time.

Admin Console field label: Log Files To Retain

Default: 7


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.)

Admin Console field label: Minimum File Size

Units: kilobytes

Default: 500

Minimum: 1

Maximum: 65535


The name of the file that stores current log messages. Usually it is a computed value based on the name of the parent of this MBean. For example, for a server log it is serverName.log.

However, if name of the parent cannot be obtained for some reason, then the name is weblogic.log.

A relative pathname is relative to the server's root directory.

Admin Console field label: Server File Name

Required: no

Default: weblogic.log


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.

Admin Console field label: File Time Span

Units: hours

Default: 24

Minimum: 1


The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.

Required: no


Optional information that you can include to describe this configuration.

Required: no


Limits the number of files that a server creates to store old messages to the maximum number specified in FileCount. After the server reaches this limit, it deletes the oldest log file and creates a new log file with the latest suffix.

If you do not enable this option, the server creates new files indefinitely. You must clean up these files as you require.

This value is relevant only if you specify a file rotation type of SIZE or TIME.

Admin Console field label: Limit Number of Retained Log Files

Default: false

Secure value: false


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. Thereafter, the server renames the log file at an interval that you specify in FileTimeSpan.

Use the following format: k:mm, where

  • k is the hour in a 24-hour format.

  • mm is the minute

If the specified time has already past, then the server starts its file rotation immediately.

By default, the rotation cycle begins immediately.

Admin Console field label: Rotation Time

Required: no

Default: 00:00


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.

  • SIZE . When the log file reaches the size that you specify in FileMinSize, the server renames the file as FileName.n.

  • 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.

Admin Console field label: Rotation Type

Required: no

Default: bySize


Skip navigation bar  Back to Top Previous Next