Store-and-Forward Agents: JMS Logging
Configuration Options Advanced Configuration Options Related Tasks Related Topics
Use this page to change the default name of this SAF agent's message log file or to configure criteria for moving (rotating) old message logs to a separate file.
Name Description Log file name
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
However, if the name of the parent cannot be obtained, the file name is
weblogic.log. If you specify a relative pathname, it is interpreted as relative to the server's root directory.
To include a time and date stamp in the file name when the log file is rotated, add
java.text.SimpleDateFormatvariables to the file name. Surround each variable with percentage (
For example, if the file name is defined to be
myserver_%yyyy%_%MM%_%dd%_%hh%_%mm%.log, the log file will be named
When the log file is rotated, the rotated file name contains the date stamp. For example, if the log file is rotated on 2 April, 2003 at 10:05 AM, the log file that contains the old messages will be named
If you do not include a time and date stamp, the rotated log files are numbered in order of creation. For example,
Criteria for moving old log messages to a separate file.
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.
When the log file reaches the size that you specify in
FileMinSize, the server renames the file as
At each time interval that you specify in
TimeSpan, the server renames the file as
After the server renames a file, subsequent messages accumulate in a new file with the name that you specified in
Rotation 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.nand create a new one to store subsequent messages. (Requires that you specify a file rotation type of
Begin 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. Thereafter, the server renames the log file at an interval that you specify in File Time Span.
If the specified time has already past, the server rotates the log file at the next scheduled interval that you specify.
Use the following format:
is the hour in a 24-hour format.
is the minute
The interval (in hours) at which the server saves old log messages to another file. (Requires that you specify a file rotation type of
Limit number of retained files
Indicates whether to limit the number of log files that this server instance creates to store old messages. (Requires that you specify a file rotation type of
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 and you must clean up these files as you require.
Files to retain
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.)
Log file rotation directory
The directory where the rotated log files will be stored. By default the rotated files are stored in the same directory where the log file is stored.
Rotate log file on startup
Specifies whether a server rotates its log file during its startup cycle.
Advanced Configuration Options
Name Description Logging implementation
Specifies whether the server logging is based on a Log4j implementation. By default, WebLogic logging uses an implementation based on the Java Logging APIs which are part of the JDK.
Applications that use the WebLogic Message Catalog framework or the NonCatalogLogger will not be affected by the underlying Logging implementation.
- Configure SAF agent JMS message log rotation
- Configure SAF queue message logging
- Configure SAF topic message logging
- View and configure logs