I'm fairly sure failure to match a rule should not result in a MessageRouterException. However, failure to compile the expression would result in an exception. Are you sure you have the expression right?
I think you need to work out why it is trying to route to the DLQ (bad expression perhaps?) and then why routing to the DLQ is failing. So it seems like you have 2 issues there.
Thanks for reply.
I am using <route-to expression="xxxx" multiple times in my service for comparing the content of different element.
If criteria is matching then i get no exception , but if content in the expression is not matching then i am getting an MessageRouterException.
The xpath which i am specifying in expression will always compares with the content of incoming message.
I have right expression defined.