Administration Console Online Help

Configure JMS server
message log rotation

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:

If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).

On the Summary of JMS Servers page, click
the JMS server you want to configure.

Click the Logging tab.

To change the default log file name, in the Log file
name field enter 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.

To move old
messages to another file when the current log file reaches a specific
size:

In the
Rotation Type list box, choose By
Size.

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.

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.

To move old
messages to another log file at specific time intervals, define the
following options:

In the
Rotation Type list box, choose By Time.

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.

In the
Rotation Interval field, enter the interval
at which the JMS server saves old messages to another file.

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.

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.

Click
Save.

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.