Network Deployment (Distributed operating systems), v8.0 > Troubleshoot and support > Troubleshoot web services > Detecting and fixing problems with WS-ReliableMessaging
Diagnosing and recovering a WS-ReliableMessaging outbound sequence that is in retransmitting state
You have to resolve a sequence in retransmitting state, because messages are backing up awaiting delivery to the target service. The retransmission might be due to a network failure, or a failure of the target server. The problem should resolve automatically, but you might want to investigate the cause to speed up recovery. To resolve a sequence in retransmitting state...
Procedure
- Check for network failures.
- If no network failures are found, look up the target endpoint address (URI) for the sequence to determine the owner of the target service, then contact the owner to check if the target server is available.
The target endpoint address is shown in the Outbound sequences settings form. Use the admin console to navigate to this form, as described in Detecting and fixing problems with WS-ReliableMessaging.
- After the communication link between the two servers is re-established, use the runtime panels to confirm that messages in the sequence are now being delivered.
Diagnosing the problem when a reliable messaging source cannot deliver its messages
Delete a failed WS-ReliableMessaging outbound sequence
WS-ReliableMessaging
Add assured delivery to web services through WS-ReliableMessaging
Detecting and fixing problems with WS-ReliableMessaging