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