If you know the sequence identifier, and the target URI for the
messages, you 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.
About this task
To diagnose this problem, complete the following steps:
Procedure
- 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 or . 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.