Outbound sequence collection

Outbound sequence collection

This page displays the collection of outbound sequences for the current scope. Outbound sequences are used to transmit messages reliably from the local application to the remote endpoint. Each sequence has a unique identifier.
To view this pane in the console, click one of the paths to this panel. For example Servers > Server Types > WebSphere application servers > server_name > [Additional Properties] Reliable messaging state > Runtime > Outbound sequences .
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 to act on, then use the buttons provided.
To change what entries are listed, or to change what information is shown for entries in the list, use the Filter settings.
The WS-ReliableMessaging runtime panels are available at many different scopes within the admin console.
See WS-ReliableMessaging - admin console panels.
The following icons are displayed here and on several other reliable messaging runtime panels:

OK Everything here, and (if there is a link) in all runtime panels below this link, is running normally.

Warning Something here, or (if there is a link) in one of the runtime panels below this link, is in an unusual state and we might have to take some action to resolve it.
For example, the system might be awaiting a response from an endpoint. In this case, either the response will be received (in which case we need take no action and the runtime information will be updated to "OK") or the reliable messaging destination has stopped acknowledging messages (in which case we have to take some action to resolve the failed sequence).

Error There is a definite error that take some action to resolve, either here or (if there is a link) in one of the runtime panels below this link.

Note that for troubleshooting purposes you only have to follow links to the sub-panels if states other than "OK" are displayed.

If reliable messaging is running on a cluster, when you examine the runtime state of inbound or outbound sequences you see multiple entries for each sequence. This is because, although reliable messaging only binds to one messaging engine in a cluster, the runtime panel is calculating and displaying the sequence information once for every cluster member.
Ignore the duplicate entries. Note that the slight differences in the statistics being displayed for each duplicate entry is due to the entries being created sequentially, while polling for messages continues.

Sequence identifier

This URI is the unique identifier for the sequence.

Associated application

The application that created the sequence.

Target endpoint URI

The destination to which messages are transmitted.

Message depth

The count of messages, held by the reliable messaging layer, that have not yet been transferred.

Messages sent

The total count of messages sent by the application for this sequence.

Details

The current state of the sequence. "Establishing" indicates that the sequence is awaiting a CreateSequenceResponse message from the reliable messaging destination; "Active" indicates that the sequence has been established; "Cannot contact the remote endpoint" indicates that the sequence has been established but the reliable messaging destination has stopped acknowledging messages; "Sequence closing" indicates that the sequence is closing and will accept no new messages; "Sequence closed" indicates that the sequence has been closed and will accept no new messages; "Sequence terminating" indicates that the sequence is terminating and will accept no new messages; "The inbound side has lost state in a terminate" indicates that the sequence has terminated with unacknowledged messages outstanding; "The sequence has timed out" indicates that the sequence has timed out.

Status

The icon indicates "OK", "Warning" or "Error" as previously described on this page. A more precise indication of the sequence state is given in the "Details" column.

Buttons

Re-allocate messages Re-allocate the messages on the selected sequences to new sequences.
Export unsent messages Export the messages from the selected sequences to .zip files. If we select any sequences that have no messages to export, a warning or error message is displayed.
Close sequence Close the selected sequences and send a CloseSequence message to indicate that the sequence is complete and will not be sending any further messages. The close protocol does not delete the resources for the sequence, so we can still access any undispatched or unsent messages. If using V1.0 of the WS-ReliableMessaging spec (which does not support this option) an error message is displayed.
See about the reliable messaging close protocol, see WS-ReliableMessaging: supported specifications and standards.
Terminate sequence Close the selected sequences and send a TerminateSequence message to indicate that the sequence is complete and will not be sending any further messages. The terminate protocol deletes all resources for the sequence.
See about the reliable messaging terminate protocol, see WS-ReliableMessaging: supported specifications and standards.
Delete sequence Delete the selected sequences without sending a TerminateSequence message.

Related tasks

Detecting and fixing problems with WS-ReliableMessaging

Related

WS-ReliableMessaging - admin console panels

	OK	Everything here, and (if there is a link) in all runtime panels below this link, is running normally.
	Warning	Something here, or (if there is a link) in one of the runtime panels below this link, is in an unusual state and we might have to take some action to resolve it. For example, the system might be awaiting a response from an endpoint. In this case, either the response will be received (in which case we need take no action and the runtime information will be updated to "OK") or the reliable messaging destination has stopped acknowledging messages (in which case we have to take some action to resolve the failed sequence).
	Error	There is a definite error that take some action to resolve, either here or (if there is a link) in one of the runtime panels below this link.

Re-allocate messages	Re-allocate the messages on the selected sequences to new sequences.
Export unsent messages	Export the messages from the selected sequences to .zip files. If we select any sequences that have no messages to export, a warning or error message is displayed.
Close sequence	Close the selected sequences and send a CloseSequence message to indicate that the sequence is complete and will not be sending any further messages. The close protocol does not delete the resources for the sequence, so we can still access any undispatched or unsent messages. If using V1.0 of the WS-ReliableMessaging spec (which does not support this option) an error message is displayed. See about the reliable messaging close protocol, see WS-ReliableMessaging: supported specifications and standards.
Terminate sequence	Close the selected sequences and send a TerminateSequence message to indicate that the sequence is complete and will not be sending any further messages. The terminate protocol deletes all resources for the sequence. See about the reliable messaging terminate protocol, see WS-ReliableMessaging: supported specifications and standards.
Delete sequence	Delete the selected sequences without sending a TerminateSequence message.