Thanks, as I can read the camel log component exists in the first place to
log out the exchange object and not to log stack traces.
--
View this message in context:
http://camel.465427.n5.nabble.com/Exception-in-Exchange-is-null-tp5717324p5717337.html
Sent from the Camel - Users mailing list
null}
> , BodyType:IllegalStateException
> , Body:java.lang.IllegalStateException: Moving files failed!
> , Out: null
> ]
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Exception-in-Exchange-is-null-tp5717324p5717333.html
> Sent from the Camel
tion=0, JMSXGroupID=null}
, BodyType:IllegalStateException
, Body:java.lang.IllegalStateException: Moving files failed!
, Out: null
]
--
View this message in context:
http://camel.465427.n5.nabble.com/Exception-in-Exchange-is-null-tp5717324p5717333.html
Sent from the Camel - Users mailing list archive at Nabble.com.
r handler is done, the
caused exception is restored and propagated back to the caller.
So you need to get the exception from the property.
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Exception-in-Exchange-is-null-tp5717324p5717329.html
>
Thanks you Claus, but I have just checked that the exception object
is still null even though handled(false) [default].
--
View this message in context:
http://camel.465427.n5.nabble.com/Exception-in-Exchange-is-null-tp5717324p5717329.html
Sent from the Camel - Users mailing list archive at
> .to("log:errorLog?level=ERROR&showAll=true&multiline=true&showStackTrace=true");
>
> What is the right way to log the stack trace into the log file by the camel
> log component? But
> take into account that JMS is in use.
>
> We are using version 2.10.0 .
true");
What is the right way to log the stack trace into the log file by the camel
log component? But
take into account that JMS is in use.
We are using version 2.10.0 .
Cheers
Hilde
--
View this message in context:
http://camel.465427.n5.nabble.com/Exception-in-Exchange-is-null-tp5717324.h
