Thanks for the response Abhishek. I was using version 2.18. The release
notes mentions that there is a bug in the hystrix fallback implementation.
However, upon moving to v2.18.3, it worked magically!
On Wed, Mar 22, 2017 at 9:17 PM, Abhishek.Jha09 <abhi...@gmail.com> wrote:
> Hi Priyanka,
>
> So, as it happens, the exceptions captured by hystrix are present as a
> property of the exchange if fallback is defined otherwise, you can get it
> directly from exchange. Try peeking inside exchange.getProperties() and
> after you trigger the route and exchange.getException().
>
> FYI, here's the logs generated in my case-
>
>
> 09:39| INFO | CamelLogger.java 159 | Before call to endpoint
> 09:39| INFO | CamelLogger.java 159 | Slow processing start:
> hystrix-my-key-1
> {CamelMessageHistory=[DefaultMessageHistory[routeId=route1,
> node=hystrix1],
> DefaultMessageHistory[routeId=route1, node=log1],
> DefaultMessageHistory[routeId=route1, node=to1],
> DefaultMessageHistory[routeId=route2, node=log4],
> DefaultMessageHistory[routeId=route2, node=delay1]],
> CamelCorrelationId=***********, CamelCreatedTimestamp=************,
> CamelRouteStop=true, CamelToEndpoint=direct://slow}
> com.netflix.hystrix.exception.HystrixRuntimeException: hystrix1 timed-out
> and no fallback available.
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.
> com/Exception-handling-with-Hystrix-EIP-tp5795811p5795991.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
