camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Tombs (JIRA)" <>
Subject [jira] [Commented] (CAMEL-4383) StreamResequencer logs unhandled Exceptions at DEBUG level
Date Tue, 30 Aug 2011 00:04:37 GMT


David Tombs commented on CAMEL-4383:

Thanks for the quick fix!

> StreamResequencer logs unhandled Exceptions at DEBUG level
> ----------------------------------------------------------
>                 Key: CAMEL-4383
>                 URL:
>             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, 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:


View raw message