Messages accumulate in a single file. You must erase the
contents of the file when the size is too large. Note that WebLogic
Server sets a threshold size limit of 500 MB before it forces a
hard rotation to prevent excessive log file growth.

SIZE

When the log file reaches the size that you specify in
FileMinSize, the server renames the file as
SERVER_NAME.lognnnnn.

TIME

At each time interval that you specify in TimeSpan,
the server renames the file as
SERVER_NAME.lognnnnn.

After the server renames a file, subsequent messages accumulate
in a new file with the name that you specified as the log file
name.

The size (1 - 65535 kilobytes) that triggers the server to move
log messages to a separate file. The default is 500 kilobytes.
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 SERVER_NAME.lognnnnn and
create a new one to store subsequent messages. (Requires that you
specify a file rotation type of Size.)

The maximum number of log files that the server creates when it
rotates the log. This number does not include the file that the
server uses to store current messages. (Requires that you enable
Number of Files Limited.)

This specifies the format of the HTTP log file. Both formats are
defined by the W3C. With the extended log format, you use server
directives in the log file to customize the information that the
server records.