Oracle Fusion Middleware Administration Console Online Help for Oracle WebLogic Server 14.1.1.0.0
F18247-03
![]() ![]() ![]() ![]() |
Diagnostics: View JMS Log Table
Column Display Related Tasks Related Topics
This page shows you the latest contents of the JMS log file.
To select log messages generated during a specific time interval, or to enter a filter expression, select Customize this table. You can set the following customizations:
- Start of the custom time interval during which you want to be able to select messages for viewing. Use a date and 24-hour format expressed as
mm/dd/yy hh:mm:ss
. For example,01/15/10 14:30:00
.- End of the custom time interval during which you want messages displayed for selection. Use a date and 24-hour format expressed as
mm/dd/yy hh:mm:ss
. For example,01/18/10 22:00:00
.- Filter expression, which is specified as a string in the WLDF Query Language. The query language supports the Boolean operators
AND
,OR
, andNOT
, and also supports relational operators. When creating a filter expression, note the following:
- Each of the different log types has a different set of column names that can be specified in the WLDF Query Expression. For example, the server log and domain log have the Severity and Message ID columns, but the events log and metrics log do not.
- The names of each column on this page are not identical to the corresponding column names in the WLDF Archive. Therefore, when constructing a filter expression that includes a column name, you must specify the column name as it appears in the WLDF Archive. For example, a filter expression that specifies data in the Transaction ID column uses the column name
TXID
in that expression. Refer to the description of each column name below for the corresponding column name in the WLDF Archive.- For more information about the valid column names that can be used in filter expressions for each log type, including examples, see "Data Store Column Names" in Configuring and Using the Diagnostics Framework for Oracle WebLogic Server (link at bottom of this help topic).
Column Display
You can show fewer or additional data points on this page by expanding Customize this table and modifying the Column Display list. Each data point displays in its own table column.
The following table lists all of the data points that you can display in columns on this page.
Name Description Date The date and time the message log record is generated.
When specifying a WLDF query expression to filter this table, note that this column corresponds to the JMSMessageLog
DATE
column in the WLDF Archive.Transaction ID The transaction identifier for the transaction with which the message is associated.
When specifying a WLDF query expression to filter this table, note that this column corresponds to the JMSMessageLog
TXID
column in the WLDF Archive.Context ID A unique identifier for a request or unit of work flowing through the system. It is included in the JMS message log to provide a correlation between events belonging to the same request.
When specifying a WLDF query expression to filter this table, note that this column corresponds to the JMSMessageLog
CONTEXTID
column in the WLDF Archive.Timestamp To aid in troubleshooting high-traffic applications, the date and time the message log record is generated is displayed in milliseconds.
When specifying a WLDF query expression to filter this table, note that this column corresponds to the JMSMessageLog
TIMESTAMP
column in the WLDF Archive.Nano Timestamp To aid in troubleshooting high-traffic applications, the date and time the message log record is generated is displayed in nanoseconds.
When specifying a WLDF query expression to filter this table, note that this column corresponds to the JMSMessageLog
NANOTIMESTAMP
column in the WLDF Archive.Message ID The unique identifier assigned to the message.
When specifying a WLDF query expression to filter this table, note that this column corresponds to the JMSMessageLog
JMSMESSAGEID
column in the WLDF Archive.Correlation ID A user-defined identifier for the message, often used to correlate messages about the same subject.
When specifying a WLDF query expression to filter this table, note that this column corresponds to the JMSMessageLog
JMSCORRELATIONID
column in the WLDF Archive.Destination The fully-qualified name of the JMS destination for the message.
When specifying a WLDF query expression to filter this table, note that this column corresponds to the JMSMessageLog
DESTINATION
column in the WLDF Archive.Event The name of the message life cycle event that triggered the log entry.
When specifying a WLDF query expression to filter this table, note that this column corresponds to the JMSMessageLog
EVENT
column in the WLDF Archive.User ID The ID of the user who generated the message.
When specifying a WLDF query expression to filter this table, note that this column corresponds to the JMSMessageLog
USERID
column in the WLDF Archive.Consumer If the message consumed was on a queue or the consumer was a non-durable subscriber for a topic, this will include information about the origin of the message consumer and the identifier for the consumer known to the JMS server. If the consumer is a durable subscriber, this will also include the client ID for the connection and the subscription name.
When specifying a WLDF query expression to filter this table, note that this column corresponds to the JMSMessageLog
MESSAGECONSUMER
column in the WLDF Archive.Selector The message Selector argument from the JMS API.
When specifying a WLDF query expression to filter this table, note that this column corresponds to the JMSMessageLog
SELECTOR
column in the WLDF Archive.Message The content of the message body.
When specifying a WLDF query expression to filter this table, note that this column corresponds to the JMSMessageLog
MESSAGE
column in the WLDF Archive.
- View and configure logs
- Customize the log entries table
- Configure JMS server message log rotation
- Configure topic message logging
- Configure queue message logging
- Configure JMS template message logging
- Uniform distributed queues - configure message logging
- Uniform distributed topics - configure message logging
![]() |