Messages [Collection]
The messages on the message point.
To view this page in the console, click one of the following paths:
To browse or change the properties of a listed item, select its name in the list.
To act on one or more of the listed items, select the check boxes next to the names of the items that you want to act on, then use the buttons provided.
To change which entries are listed, or to change the level of detail that is displayed for those entries, use the Filter settings.
A snapshot of the set of messages queued on the message point. You can display or remove selected messages from the list.
Because this is a snapshot of the message point, a message listed might no longer exist when you attempt to display it or act on it.
- Position
- The position of the message on the message point list.
- Messaging engine message identifier
- Messaging engine message identifier.
- State
- The current state of the message related to a transaction that
the message is part of. If the message is part of a transaction, the transaction identifier is shown in the Transaction ID field. The
possible states are:
- Available
- The message is available for consumption.
- Locked
- The message is currently unavailable. The message is in this state temporarily, possibly because it is being consumed by a non-transacted consumer.
- Remote lock
- The message is currently locked to a consumer attached to another, remote, messaging engine in the bus. The message will remain locked until the remote messaging engine responds with a decision on the message. If the remote messaging engine is stopped, the message will remain locked until the messaging engine is restarted. A corresponding message request for a "known remote queue point" will identify the remote messaging engine that is making the request.
- Removing
- The message is currently being removed under a transaction. The message will be in this state until the transaction commits or rolls back. If this state persists, investigate the state of the transaction identified by Transaction ID.
- Committing
- The message is currently being added under a transaction. The message will be in this state until the transaction commits or rolls back. If this state persists, investigate the state of the transaction identified by Transaction ID.
- Pending retry
- The message is currently unavailable before being eligible for a retry. This might be because a message-driven bean is configured to delay failing message retries.
- Blocked
- This message is currently unavailable because the message point is blocked by the first message on the queue. The first message has reached its maximum failed delivery limit but no exception destination is configured. Identify the first message and resolve the problem that is preventing it from being consumed.
- Transaction ID
- The local transaction identifier of the transaction that this message is currently part of.