Inbound sequence collection
This page displays the collection of inbound sequences for the current scope. Each inbound sequence is used to receive messages that have been transmitted reliably.
To view this page in the console, click one of the paths to this panel. For example Servers > Server Types > WebSphere application servers > server > [Additional Properties] Reliable messaging state > Runtime > Inbound 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 administrative console. See WS-ReliableMessaging - administrative console panels.
The following icons are displayed here and on several other reliable messaging runtime panels:
| Icon | Name | Description |
|---|---|---|
|
| 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 we must 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 we only have to follow links to the sub-panels if states other than "OK" are displayed.
We might see more sequences than you expect, due to sequence reallocation. If a sequence is reallocated, the original and new sequences are both visible.
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.
(ZOS) When we examine the runtime state of inbound or outbound sequences we might see multiple entries for each sequence. This is because, although reliable messaging only binds to one messaging engine, the runtime panel is calculating and displaying the sequence information once for every servant region.
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 is receiving messages from the sequence.
- Message depth
- The count of messages, held by the reliable messaging layer, that have not yet been transferred.
- Messages received
- The total count of application messages received for the sequence since its creation.
- Details
- The current state of the sequence. "Connected" indicates that the sequence has been established; "Awaiting redelivery of a missing msg." indicates that there is a gap in the sequence; "Closed" indicates that the sequence has been closed; "Failed due to missing message" indicates that the sequence terminated with a gap in the sequence.
- 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
| Button | Description |
|---|---|
| Dispatch messages to application | Dispatch the messages on the selected sequences to the associated applications. |
| Export undispatched messages | Export the messages from the selected sequences to compressed 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 we are using Version 1.0 of the WS-ReliableMessaging specification (which does not support this option) an error message is displayed. For more information 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. For more information about the reliable messaging terminate protocol, see WS-ReliableMessaging: supported specifications and standards.
Terminate sequences only if necessary. Refer to the description of the Delete sequence button for more information. |
| Delete sequence and messages | Delete the selected sequences and all their messages. Use this in cases where the remote endpoint is unable to respond to any reliable messaging protocol messages, and therefore the sequence cannot be closed or terminated.
Delete or terminate sequences only if necessary. If we delete or terminate an active sequence, the resulting messaging behavior is unpredictable and can cause loss of messages. If we are not sure whether we can safely delete or terminate a sequence, do not delete or terminate it; the system automatically deletes sequences that have been inactive for 12 hours. |
Related: