Administration Console Online Help
|
Server --> Logging --> Rotation
Tasks Additional Documentation Attributes
Overview
The Server—>Logging—>Rotation tab determines when the server moves old log messages into another file. You can specify that the server does one of the following:
- Places all server log messages in a single file.
- Moves old messages to a new file when the current log file reaches a specific size.
- Moves old messages to a new file at specific time intervals.
Note: 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.
Tasks
Specifying Log File Rotation
Viewing Server Logs
Specifying General Log File Settings
Specifying HTTP Log File Settings for a Server
Specifying the JDBC Log File
Specifying the Transaction Log File Location (Prefix)
Additional Documentation
(Requires an Internet connection.)
Using Log Messages to Manage WebLogic Servers in the WebLogic Server Administration Guide.
Attributes
Attribute Label
|
Description
|
Value Constraints
|
Rotation Type
|
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.
MBean: weblogic.management. configuration.LogMBean
Attribute: RotationType
|
Default: "none"
Valid values:
Configurable: yes
Dynamic: yes
Readable: yes
Writable: yes
|
File Min Size
|
The file 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.
MBean: weblogic.management. configuration.LogMBean
Attribute: FileMinSize
|
Units: kilobytes
Minimum: 1
Maximum: 65535
Default: 500
Configurable: yes
Dynamic: yes
Readable: yes
Writable: yes
|
Rotation Time
|
Determines the start time 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
Configurable: yes
Dynamic: yes
Readable: yes
Writable: yes
|
File Time Span
|
The interval (in hours) at which the server saves old log messages to another file. This value is relevant only if you use the time-based rotation type.
MBean: weblogic.management. configuration.LogMBean
Attribute: FileTimeSpan
|
Units: hours
Minimum: 1
Default: 24
Configurable: yes
Dynamic: yes
Readable: yes
Writable: yes
|
Number Of Files Limited
|
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.LogMBean
Attribute: NumberOfFilesLimited
|
Default: false
Dynamic: yes
Readable: yes
Writable: yes
|
File Count
|
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.LogMBean
Attribute: FileCount
|
Default: 7
Configurable: yes
Dynamic: yes
Readable: yes
Writable: yes
|