You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2009/03/11 15:02:41 UTC
[jira] Created: (CAMEL-1449) DeadLetterChannel - Should not mark an
Exchange as handled if no handled policy was configured
DeadLetterChannel - Should not mark an Exchange as handled if no handled policy was configured
----------------------------------------------------------------------------------------------
Key: CAMEL-1449
URL: https://issues.apache.org/activemq/browse/CAMEL-1449
Project: Apache Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.0.0
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Priority: Critical
Fix For: 2.0.0
By default the DLC will mark an Exchange as been handled if it could not redeliver it and will log it at ERROR level = the default DLC settings.
But it should *not* mark the Exchange as handled, if there has not been configured to do so in
- DLC.handled(true)
- onException(Foo.class).handled(true)
So in that regard it will still LOG it at ERROR level but the Exchange seen by the original caller, or eg a FileConsumer will still se the Exchange as both failed and *not handled*.
Only if end user configure the route to use handled(true) it should mark the Exchange as handled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-1449) DeadLetterChannel - Should not mark an
Exchange as handled if no handled policy was configured
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-1449:
-------------------------------
Fix Version/s: 2.0-M1
As it changes semantics a little I need to get it in M1 so end users can try it out first.
The semantic change is: The DLC will by default *not* mark an Exchange as handled if it failed all redelivery attempts and move it to its default error queue = just logging it at ERROR level.
> DeadLetterChannel - Should not mark an Exchange as handled if no handled policy was configured
> ----------------------------------------------------------------------------------------------
>
> Key: CAMEL-1449
> URL: https://issues.apache.org/activemq/browse/CAMEL-1449
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.0.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Critical
> Fix For: 2.0-M1, 2.0.0
>
>
> By default the DLC will mark an Exchange as been handled if it could not redeliver it and will log it at ERROR level = the default DLC settings.
> But it should *not* mark the Exchange as handled, if there has not been configured to do so in
> - DLC.handled(true)
> - onException(Foo.class).handled(true)
> So in that regard it will still LOG it at ERROR level but the Exchange seen by the original caller, or eg a FileConsumer will still se the Exchange as both failed and *not handled*.
> Only if end user configure the route to use handled(true) it should mark the Exchange as handled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-1449) DeadLetterChannel - Should not mark
an Exchange as handled if no handled policy was configured
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-1449.
--------------------------------
Resolution: Won't Fix
We change default in 2.0 to have no error handler by default
> DeadLetterChannel - Should not mark an Exchange as handled if no handled policy was configured
> ----------------------------------------------------------------------------------------------
>
> Key: CAMEL-1449
> URL: https://issues.apache.org/activemq/browse/CAMEL-1449
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.0.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Critical
> Fix For: 2.0.0
>
>
> By default the DLC will mark an Exchange as been handled if it could not redeliver it and will log it at ERROR level = the default DLC settings.
> But it should *not* mark the Exchange as handled, if there has not been configured to do so in
> - DLC.handled(true)
> - onException(Foo.class).handled(true)
> So in that regard it will still LOG it at ERROR level but the Exchange seen by the original caller, or eg a FileConsumer will still se the Exchange as both failed and *not handled*.
> Only if end user configure the route to use handled(true) it should mark the Exchange as handled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1449) DeadLetterChannel - Should not mark
an Exchange as handled if no handled policy was configured
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50442#action_50442 ]
Claus Ibsen commented on CAMEL-1449:
------------------------------------
Maybe the default DLC that just logs at ERROR should *not* mark the Exchange as handled.
Then the individual onException can do it on their will
> DeadLetterChannel - Should not mark an Exchange as handled if no handled policy was configured
> ----------------------------------------------------------------------------------------------
>
> Key: CAMEL-1449
> URL: https://issues.apache.org/activemq/browse/CAMEL-1449
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.0.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Critical
> Fix For: 2.0.0
>
>
> By default the DLC will mark an Exchange as been handled if it could not redeliver it and will log it at ERROR level = the default DLC settings.
> But it should *not* mark the Exchange as handled, if there has not been configured to do so in
> - DLC.handled(true)
> - onException(Foo.class).handled(true)
> So in that regard it will still LOG it at ERROR level but the Exchange seen by the original caller, or eg a FileConsumer will still se the Exchange as both failed and *not handled*.
> Only if end user configure the route to use handled(true) it should mark the Exchange as handled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-1449) DeadLetterChannel - Should not mark an
Exchange as handled if no handled policy was configured
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-1449:
-------------------------------
Comment: was deleted
(was: As it changes semantics a little I need to get it in M1 so end users can try it out first.
The semantic change is: The DLC will by default *not* mark an Exchange as handled if it failed all redelivery attempts and move it to its default error queue = just logging it at ERROR level.)
> DeadLetterChannel - Should not mark an Exchange as handled if no handled policy was configured
> ----------------------------------------------------------------------------------------------
>
> Key: CAMEL-1449
> URL: https://issues.apache.org/activemq/browse/CAMEL-1449
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.0.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Critical
> Fix For: 2.0.0
>
>
> By default the DLC will mark an Exchange as been handled if it could not redeliver it and will log it at ERROR level = the default DLC settings.
> But it should *not* mark the Exchange as handled, if there has not been configured to do so in
> - DLC.handled(true)
> - onException(Foo.class).handled(true)
> So in that regard it will still LOG it at ERROR level but the Exchange seen by the original caller, or eg a FileConsumer will still se the Exchange as both failed and *not handled*.
> Only if end user configure the route to use handled(true) it should mark the Exchange as handled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-1449) DeadLetterChannel - Should not mark an
Exchange as handled if no handled policy was configured
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-1449:
-------------------------------
Fix Version/s: (was: 2.0-M1)
> DeadLetterChannel - Should not mark an Exchange as handled if no handled policy was configured
> ----------------------------------------------------------------------------------------------
>
> Key: CAMEL-1449
> URL: https://issues.apache.org/activemq/browse/CAMEL-1449
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.0.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Critical
> Fix For: 2.0.0
>
>
> By default the DLC will mark an Exchange as been handled if it could not redeliver it and will log it at ERROR level = the default DLC settings.
> But it should *not* mark the Exchange as handled, if there has not been configured to do so in
> - DLC.handled(true)
> - onException(Foo.class).handled(true)
> So in that regard it will still LOG it at ERROR level but the Exchange seen by the original caller, or eg a FileConsumer will still se the Exchange as both failed and *not handled*.
> Only if end user configure the route to use handled(true) it should mark the Exchange as handled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.