Hi Yes you can usually control the level with the options on the error handler. And turn of the message history etc.
Though we could maybe look into see if we can improve something in Camel too, can you show that stacktrace? On Wed, Jul 8, 2015 at 11:05 PM, MC <2320...@gmail.com> wrote: > Hi, > > I am using Simple expression (camel version 2.15.2) which in somecases > throws CamelExecutionException. I am handling the exceptions, but stacktrace > (logging it to logs/console) contains payload information where it is > failing on. I understand its good thing for development. But in production > payload contains sensitive information which I don't want to log along with > stacktrace. I looked at the camel code (RuntimeExchangeException constructs > the exception message with exchange if it is not null) and there is no > option to skip the payload from exception message. Only way to avoid it is > to print root cause rather than the wrapper exception. This situation could > be true with any core components which throws CamelExectionException if i > understand camel correctly. > > Is there a way to control exception messages? > > Thanks in advance > MC > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-Execution-Exception-tp5769004.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
