Manual Chapter : Route Status
Applies To:Show Versions
- 17.1.0, 17.0.0, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0, 14.0.1, 14.0.0, 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0
Message has not been submitted for routing yet
Route has been found
no route found
A route has not been found
The message has been dropped by a MR::message drop command
The message was returned back to the originator because one of the MRF processing queues had reached its configured limit.
The message was routed to a connection which was no longer present.
The message was queued to be send on a connection which was closed.
The message was unable to be delivered due to an internal error. For example, out of memory.
persist key in use
Two messages routed using the same persistence key simultanously tried to create the same persistence record.
The message is a mirrored message running on a standby device and was dropped as part of routing to avoid creating an outgoing connection on the standby device.
Max retries exceeded
The message was returned to the originator because the latest attempt to retry routing exceeded the configured max retry count.