Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# Configure JMS server message log rotation

Before you begin

- Create JMS servers
- Configure queue message logging
- Configure topic message logging

After you create a JMS server, you can change the default name of its log file, as well as configure criteria for moving (rotating) old log messages to a separate file. A JMS server's log file contains the basic events that a JMS message traverses through, such as message production, consumption, and removal. However, logging must be enabled on destinations in the JMS modules targeted to this JMS server.

The content of the message log always includes message ID and correlation ID, but you can also configure information like message type and user properties on specific destinations.

To configure a log file parameters for a JMS server:

1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
2. In the Administration Console, expand Services > Messaging and select JMS Servers.
3. On the Summary of JMS Servers page, click the JMS server you want to configure.
4. Click the Logging tab.
5. To change the default log file name, in the Log file name field tenter a path and filename for the JMS server log.

   Enter an absolute pathname or a pathname that is relative to the server's root directory. If you use the Node Manager to start a Managed Server, the root directory is located on the computer that hosts the Node Manager process. For more information, see A Server's Root Directory.

6. To move old messages to another file when the current log file reaches a specific size:
   1. In the Rotation Type list box, choose `By Size`.
   2. In the Rotation File Size field, enter the file size that triggers the JMS server to move log messages to a separate file. After the log file reaches the specified size, the next time the JMS server checks the file size, it will rename the current log file. After the JMS server renames the file, subsequent messages accumulate in a new file named `filename.log`.
   3. If you want to limit the number of log files that the JMS server creates to store old log messages, select the Limit Number of Retained Files check box. Then in the Files to Retain field, enter the maximum number of files. If the JMS server receives additional log messages after reaching the capacity of the last log file, it overwrites the oldest log file.
7. To move old messages to another log file at specific time intervals, define the following options:
   1. In the Rotation Type list box, choose `By Time`.
   2. In the Begin Rotation Time field, enter the start time.

      Use the following format: `hh`:`mm`, where `hh` is the hour in a 24-hour format and `mm` is the minute. At the time that you specify, the JMS server rotates the current log file. If the time that you specify is already past, the JMS server starts its file rotation immediately. Thereafter, the JMS server rotates the log file at an interval that you specify in Rotation Interval.

   3. In the Rotation Interval field, enter the interval at which the JMS server saves old messages to another file.
   4. If you want to limit the number of log files that the JMS server creates to store old log messages, select the Limit Number of Retained Log Files check box. Then in the Files to Retain field, enter the maximum number of files. If the JMS server receives additional log messages after reaching the capacity of the last log file, it overwrites the oldest log file.

   For more information about these fields, refer to Configuration Options.

8. In the Log File Rotation Directory field, enter the directory location where the rotated log files will be stored.

   Enter an absolute pathname or a pathname that is relative to the server's root directory. By default, the rotated files are stored in the same directory where the log file is stored.

   For more information, see A Server's Root Directory.

9. To specify whether a JMS server rotates its log file during its startup cycle, select Rotate log file on startup check box.
10. Optionally, click Advanced to access the Logging Implementation field, where you can select whether the JMS 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.
11. Click Save.
12. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).

Result

After you finish

If you modified the Log file name, Log File Rotation Directory, or Rotate log file on startup fields, then you must restart the server.