Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# JMS Server: Logging

Configuration Options Advanced Configuration Options Related Tasks Related Topics

Use this page to change the default name of this JMS server's log file or to configure criteria for moving (rotating) old log messages to a separate file.

#### Configuration Options

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 `serverName.log`. 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.SimpleDateFormat` variables to the file name. Surround each variable with percentage (`%`) characters. For example, if the file name is defined to be `myserver_%yyyy%_%MM%_%dd%_%hh%_%mm%.log`, the log file will be named `myserver_yyyy_mm_dd_hh_mm.log`. 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 `myserver_2003_04_02_10_05.log`. If you do not include a time and date stamp, the rotated log files are numbered in order of creation. For example, `myserver.log00007`. MBean Attribute: `LogMBean.FileName` Changes take effect after you redeploy the module or restart the server.
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 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 `FileName.n`. `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 Attribute: `LogMBean.RotationType` Secure value: `byTime` Changes take effect after you redeploy the module or restart the server.
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.n` and create a new one to store subsequent messages. (Requires that you specify a file rotation type of `Size`.) MBean Attribute: `LogMBean.FileMinSize` Minimum value: `1` Maximum value: `65535`
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, then the server starts its file rotation immediately. Use the following format: `k:mm`, where `k` is the hour in a 24-hour format. `mm` is the minute MBean Attribute: `LogMBean.RotationTime`
Rotation interval | The interval (in hours) at which the server saves old log messages to another file. (Requires that you specify a file rotation type of `TIME`.) MBean Attribute: `LogMBean.FileTimeSpan` Minimum value: `1`
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 `SIZE` or `TIME`.) 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. MBean Attribute: `LogMBean.NumberOfFilesLimited`
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.) MBean Attribute: `LogMBean.FileCount` Minimum value: `1` Maximum value: `99999`
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. MBean Attribute: `LogMBean.LogFileRotationDir` Changes take effect after you redeploy the module or restart the server.
Rotate log file on startup | Specifies whether a server rotates its log file during its startup cycle. MBean Attribute: `LogMBean.RotateLogOnStartup` Changes take effect after you redeploy the module or restart the server.

#### 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. MBean Attribute: `LogMBean.Log4jLoggingEnabled` Changes take effect after you redeploy the module or restart the server.

Related Tasks

- Configure queue message logging
- Configure topic message logging
- Configure JMS template message logging
- View and configure logs

Related Topics

- Configuring and Managing WebLogic JMS
- Configuring Log Files and Filtering Log Messages