Hi Just started on a prototype for being able to turn on|off a message history output in the error log when Camel logs an exhausted exception.
There is a sample at: https://gist.github.com/davsclaus/5678776 The idea is to aid our end users, to let them easier spot where in a route the exception occurred. And being able to see that directly from the logs is IMHO a good idea. So from the gist link above the exception occurred at that last node, which no surprisingly is from a processor where we force throwing an exception from("seda:start") .to("log:foo") .to("log:bar") .to("log:baz") .process(new Processor() { @Override public void process(Exchange exchange) throws Exception { throw new IllegalArgumentException("Forced to dump stacktrace"); Anyway just wanted to share this. The implementation is invasive and fully backwards compatible. We can decide to leave it off by default. And allow people to turn it on. Or maybe better yet, its so useful for our end users, we may want to enable it out fo the box. We could also add more details in the error message, such as the time the exchange was created, and the duration in millis since it was created etc. And other details. We could also output the duration each message history took, so you can see that in a column. -- Claus Ibsen ----------------- www.camelone.org: The open source integration conference. Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
