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:
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.
Use the following
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
For more information about these fields, refer to Configuration Options.
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.
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.