Question

I am using until-successful in order to retry a connection several times, in the case of me the retry policy being exhausted, i would like to log the error gracefully (without raising an exception).
I’ve tried using a default-exception-strategy, like so:

<until-successful objectStore-ref="objectStore"
        deadLetterQueue-ref="ErrorHandler" maxRetries="${TMSService.numOfRetries}"
        secondsBetweenRetries="${TMSService.retrySecInterval}">
        <outbound-endpoint address="${TMSService.host}" />
    </until-successful>
    <default-exception-strategy>
        <vm:outbound-endpoint path="ErrorMsgs" />
    </default-exception-strategy>

But that still wont catch that exception, what would be the correct way to handle this?

Thanks
Thanks

Answer 1

The until-successful message processor doesn’t throw exceptions (unless a technical issue, maybe with its object store), prevents it to enqueue the message for delivery.

If you want to find out the exception that caused the last delivery error, you should find at in the exception payload of the MuleMessage that gets dispatched to your DLQ endpoint.