Why is Mule exception strategy so chatty?

Question

In my Mule app, I\'ve configured some of the flows to use a catch exception strategy in order to do some special processing. For these cases, I want to pop the error and the

Answer 1

The issue is that the built in exception strategies inherit from AbstractExceptionListener, and they all use the logException template method. The base implementation always logs at ERROR level, which is sometimes not appropriate for your application.

You can create a simple subclass of CatchMessagingExceptionStrategy that overrides the logException method, and logs however you want. Then, use it in your flow in place of the <catch-exception-strategy> like so:

<custom-exception-strategy class="com.mycompany.mule.QuietCatchExceptionStrategy">
    <!-- your message processors here -->
</custom-exception-strategy>