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 wrote:
> Hi Priyanka,
>
> So, as it happens, t
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'
