Delete a failed WS-ReliableMessaging outbound sequence
We have to resolve an outbound sequence in failed state, so that messages can again be transmitted to the target service. A sequence in failed state shows an unrecoverable error. The sequence can no longer be used. If messages are being delivered in order, then the failed sequence must be resolved before a new sequence can be established.
Deleting an outbound sequence allows the runtime environment to automatically create a new sequence the next time an application attempts to invoke a web service at the destination address that the failed sequence was targeting. To work with outbound sequences we use the administrative console runtime panels as described in Detect and fix problems with WS-ReliableMessaging.
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.
To diagnose and delete a failed outbound sequence, use the administrative console to complete the following steps:
Tasks
- In the navigation pane of the administrative console, click one of the paths to the outbound sequences collection form. For example Servers > Server Types > WebSphere application servers > server > [Additional Properties] Reliable messaging state > Runtime > Outbound sequences. The runtime state of each of the outbound sequences for the current scope is displayed in the Outbound sequence collection form.
- Examine the failure reason by clicking on the Sequence identifier field of the failed sequence. The Outbound sequences settings form is displayed. The failure reason is based on the fault message received by the sequence manager from the target server.
- If there are messages associated with the failed sequence, decide what to do with these messages. The messages might have been transmitted and received at the target server, or they might not. We might choose to delete messages from the sequence or export them to a compressed file. If we choose to delete the messages, we can either delete individual messages or we can delete all the messages.
- Optional: To delete one or more messages from a failed sequence:
- In the main pane of the Outbound sequences settings form, under the Additional Properties section, click Messages. The messages for the failed outbound sequence are listed in the Outbound message collection form.
- Select the check boxes next to the names of the messages to delete.
- Click Delete.
- Optional: To export all the remaining messages in a failed sequence:
- In the main pane of the Outbound sequence collection form, select the check box next to the name of the failed sequence.
- Click Export unsent messages. All remaining messages in the sequence are exported to a compressed file.
- Close or terminate the failed sequence.
In the WS-ReliableMessaging Version 1.1 specification, a sequence can be closed rather than terminated. This allows the final ACK state to be sent from the reliable messaging destination to the reliable messaging source. In the WS-ReliableMessaging Version 1.0 specification this does not happen, so the final ACK state might not be known at the reliable messaging source. For more information about the distinction between close and terminate, see Outbound sequence collection.
- In the main pane of the Outbound sequence collection form, select the check box next to the name of the failed sequence.
- Click Close sequence or Terminate sequence.
- Delete the failed sequence.
- In the main pane of the Outbound sequence collection form, select the check box next to the name of the failed sequence.
- Click Delete sequence.
Diagnose the problem when a reliable messaging source cannot deliver its messages Diagnose and recovering a WS-ReliableMessaging outbound sequence that is in retransmitting state WS-ReliableMessaging Add assured delivery to web services through WS-ReliableMessaging WS-ReliableMessaging: supported specifications and standards