Thank you for all the answers. I solved the problem by adding an errorHandler() to the route and disabling the logging with
.logStackTrace(false).logExhausted(false) Now I have a slightly different problem. When the upload to the server fails, I want to increase exponentially the timeout between attempts. Does the file component supports exponential backoff delays between polling for files? I saw in the documentation that it is possible to specify a fixed delay, but I couldn't find a way of specifying a different retry policy. I saw that the retry policy for the redelivering exchanges support exponential backoff, but doing the retry at the level of the route instead of the file component creates another problem, which is that I can no longer shutdown the process with CTRL^C. It seems that Camel delays the shutdown while there are exchanges in transit. Is this correct? Is there some way making Camel shutdown the server even if some routes have pending exchanges? Or even better, to specify a shutdown handler for a route, so I can cleanup pending exchanges? Thank you, Nuno -- View this message in context: http://camel.465427.n5.nabble.com/Custom-logging-of-exceptions-by-file-component-tp5735152p5735186.html Sent from the Camel - Users mailing list archive at Nabble.com.
