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:05:05 UTC
[jira] Created: (CAMEL-1036) Add ability to configure log level on
exceptions from DLC retry mechanism
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.
[jira] Work started: (CAMEL-1036) Add ability to configure log
level on exceptions from DLC retry mechanism
Posted by "Jonathan Anstey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on CAMEL-1036 started by Jonathan Anstey.
> 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.
[jira] Commented: (CAMEL-1036) Add ability to configure log level
on exceptions from DLC retry mechanism
Posted by "Jonathan Anstey (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CAMEL-1036) Add ability to configure log level
on exceptions from DLC retry mechanism
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46924#action_46924 ]
Claus Ibsen commented on CAMEL-1036:
------------------------------------
Nice feature.
Remember to document it on the wiki at::
- http://activemq.apache.org/camel/dead-letter-channel.html. There is a section for "Redelivery default values"
- And the class javadoc for: org.apache.camel.processor.RedeliveryPolicy
> 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.
[jira] Resolved: (CAMEL-1036) Add ability to configure log level on
exceptions from DLC retry mechanism
Posted by "Jonathan Anstey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Anstey resolved CAMEL-1036.
------------------------------------
Resolution: Fixed
> 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.
[jira] Commented: (CAMEL-1036) Add ability to configure log level
on exceptions from DLC retry mechanism
Posted by "Jonathan Anstey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46926#action_46926 ]
Jonathan Anstey commented on CAMEL-1036:
----------------------------------------
Added the Spring test case, updated the wiki, and improved the javadoc. Marking this one as resolved.
> 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.
[jira] Updated: (CAMEL-1036) Add ability to configure log level on
exceptions from DLC retry mechanism
Posted by "Jonathan Anstey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Anstey updated CAMEL-1036:
-----------------------------------
Fix Version/s: 1.5.1
> 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: 1.5.1, 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.