You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Jonathan Anstey (JIRA)" <ji...@apache.org> on 2008/10/30 15:17:06 UTC

[jira] Commented: (CAMEL-1036) Add ability to configure log level on exceptions from DLC retry mechanism

    [ https://issues.apache.org/activemq/browse/CAMEL-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46918#action_46918 ] 

Jonathan Anstey commented on CAMEL-1036:
----------------------------------------

Committed Java DSL changes in revision 709164. Will cook up a Spring DSL test case after lunch.

> Add ability to configure log level on exceptions from DLC retry mechanism
> -------------------------------------------------------------------------
>
>                 Key: CAMEL-1036
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1036
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core, camel-spring
>    Affects Versions: 1.5.0
>            Reporter: Jonathan Anstey
>            Assignee: Jonathan Anstey
>             Fix For: 2.0.0
>
>
> Right now, when Camel tries to redeliver an message a number of times (using the DLC), the exceptions are logged as ERROR. Sometimes though, these retries may be considered part of normal operation. I'm going to put in DSL options to configure this log level. Something like this will be possible:
> {code}
> onException(AException.class).maximumRedeliveries(5)
>             .retriesExhaustedLogLevel(LoggingLevel.DEBUG)
>             .retryAttemptedLogLevel(LoggingLevel.DEBUG)
>             .process(new MyExceptionProcessor("I got an Exception."));
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.