Diagnose the problem when a reliable messaging source cannot deliver its messages
If we know the sequence identifier, and the target URI for the messages, we can use the runtime administrative console panels to examine the sequence and determine why a reliable messaging source is not delivering its messages into the application server.
To diagnose this problem:
Tasks
- Identify the target server or cluster from the target URI.
- Use the administrative console to view the inbound sequences runtime information for the target server or cluster.
In the navigation pane, click either Servers > Server Types > WebSphere application servers > server > [Additional Properties] Reliable messaging state > Runtime > Inbound sequences or Servers > Clusters > WebSphere application server clusters > cluster_name > [Additional Properties] Reliable messaging state > Runtime > Inbound sequences. The runtime state of each of the inbound sequences for the current scope is displayed in the Inbound sequence collection form.
- Specify a filter on the runtime view of the sequences, filtering on the Sequence identifier provided by the reliable messaging source owner.
- Click on the Sequence identifier of the displayed sequence to get a more detailed view of it.
- If the sequence has failed, examine the runtime status of the failed sequence and provide the reliable messaging source owner with details of which messages have been acknowledged, so that the owner can decide whether to delete, or to process out of order, any undelivered messages.
- If the sequence has not failed, see whether there is a communications problem between the reliable messaging source and the application server.
Diagnose and recovering a WS-ReliableMessaging outbound sequence in retransmitting state Deleting a failed WS-ReliableMessaging outbound sequence WS-ReliableMessaging Add assured delivery to web services through WS-ReliableMessaging