[
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
