You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "David Tombs (JIRA)" <ji...@apache.org> on 2011/08/25 20:52:40 UTC
[jira] [Created] (CAMEL-4383) StreamResequencer logs unhandled
Exceptions at DEBUG level
StreamResequencer logs unhandled Exceptions at DEBUG level
----------------------------------------------------------
Key: CAMEL-4383
URL: https://issues.apache.org/jira/browse/CAMEL-4383
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.7.1
Environment: Linux JDK 1.6.0_20
Reporter: David Tombs
If an unhandled Exception is caught by StreamResequencer.run(), it effectively logs the Exception at DEBUG level. A thrown Exception can indicate that a delivered message was not fully processed (as is the case in my route), so this means a message is dropped with a notification in the log only at DEBUG level. This is highly undesirable in a critical route.
It should at least be logged at WARN level, and preferably should be handled using the configured ErrorHandler for the route.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4383) StreamResequencer logs unhandled
Exceptions at DEBUG level
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092213#comment-13092213 ]
Claus Ibsen commented on CAMEL-4383:
------------------------------------
See CAMEL-3783
> StreamResequencer logs unhandled Exceptions at DEBUG level
> ----------------------------------------------------------
>
> Key: CAMEL-4383
> URL: https://issues.apache.org/jira/browse/CAMEL-4383
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.7.1
> Environment: Linux JDK 1.6.0_20
> Reporter: David Tombs
> Assignee: Claus Ibsen
>
> If an unhandled Exception is caught by StreamResequencer.run(), it effectively logs the Exception at DEBUG level. A thrown Exception can indicate that a delivered message was not fully processed (as is the case in my route), so this means a message is dropped with a notification in the log only at DEBUG level. This is highly undesirable in a critical route.
> It should at least be logged at WARN level, and preferably should be handled using the configured ErrorHandler for the route.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-4383) StreamResequencer logs unhandled
Exceptions at DEBUG level
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-4383:
----------------------------------
Assignee: Claus Ibsen
> StreamResequencer logs unhandled Exceptions at DEBUG level
> ----------------------------------------------------------
>
> Key: CAMEL-4383
> URL: https://issues.apache.org/jira/browse/CAMEL-4383
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.7.1
> Environment: Linux JDK 1.6.0_20
> Reporter: David Tombs
> Assignee: Claus Ibsen
>
> If an unhandled Exception is caught by StreamResequencer.run(), it effectively logs the Exception at DEBUG level. A thrown Exception can indicate that a delivered message was not fully processed (as is the case in my route), so this means a message is dropped with a notification in the log only at DEBUG level. This is highly undesirable in a critical route.
> It should at least be logged at WARN level, and preferably should be handled using the configured ErrorHandler for the route.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4383) StreamResequencer logs unhandled
Exceptions at DEBUG level
Posted by "David Tombs (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093322#comment-13093322 ]
David Tombs commented on CAMEL-4383:
------------------------------------
Thanks for the quick fix!
> StreamResequencer logs unhandled Exceptions at DEBUG level
> ----------------------------------------------------------
>
> Key: CAMEL-4383
> URL: https://issues.apache.org/jira/browse/CAMEL-4383
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.7.1
> Environment: Linux JDK 1.6.0_20
> Reporter: David Tombs
> Assignee: Claus Ibsen
> Fix For: 2.8.1, 2.9.0
>
>
> If an unhandled Exception is caught by StreamResequencer.run(), it effectively logs the Exception at DEBUG level. A thrown Exception can indicate that a delivered message was not fully processed (as is the case in my route), so this means a message is dropped with a notification in the log only at DEBUG level. This is highly undesirable in a critical route.
> It should at least be logged at WARN level, and preferably should be handled using the configured ErrorHandler for the route.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-4383) StreamResequencer logs unhandled
Exceptions at DEBUG level
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-4383.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.9.0
2.8.1
Thanks for reporting. Should be logging at ERROR level now.
> StreamResequencer logs unhandled Exceptions at DEBUG level
> ----------------------------------------------------------
>
> Key: CAMEL-4383
> URL: https://issues.apache.org/jira/browse/CAMEL-4383
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.7.1
> Environment: Linux JDK 1.6.0_20
> Reporter: David Tombs
> Assignee: Claus Ibsen
> Fix For: 2.8.1, 2.9.0
>
>
> If an unhandled Exception is caught by StreamResequencer.run(), it effectively logs the Exception at DEBUG level. A thrown Exception can indicate that a delivered message was not fully processed (as is the case in my route), so this means a message is dropped with a notification in the log only at DEBUG level. This is highly undesirable in a critical route.
> It should at least be logged at WARN level, and preferably should be handled using the configured ErrorHandler for the route.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira