The domain's log contains messages that individual servers within the domain have forwarded. By default, only the log messages of an ERROR or higher severity are forwarded from the local servers to the domain log. To change the default, create a domain log filter.
Attribute Label
|
Description
|
Value Constraints
|
File Name
|
The name of the file that stores current log messages for the domain log. If the pathname is not absolute, the path is assumed to be relative to the domain directory. 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, wl-domain_%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 filenamennnnn, where filename is the name configured for the log file.MBean: weblogic.management.
configuration.LogMBeanAttribute: FileName
|
Default: wl-domain.log Configurable: 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.LogMBeanAttribute: RotationType
|
Default: noneValid values:
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.LogMBeanAttribute: FileMinSize
|
Units: kilobytesMinimum: 1Maximum: 65535Default: 500Configurable: yesDynamic: 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.LogMBeanAttribute: RotationTime
|
Default: 00:00Configurable: yesDynamic: 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.LogMBeanAttribute: FileTimeSpan
|
Units: hoursMinimum: 1Default: 24Dynamic: yes
|
Limit Number of Retained Log Files
|
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 overwrites the oldest file. 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.MBean: weblogic.management.
configuration.LogMBeanAttribute: NumberOfFilesLimited
|
Default: falseValid values:
Dynamic: yes
|
Log Files to Retain
|
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.MBean: weblogic.management.
configuration.LogMBeanAttribute: FileCount
|
Default: 7Dynamic: yes
|