-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TimeoutException in AbstractCommand doesn't chain its cause #1119
Comments
This was a premature optimization to save on allocations. As you brought up, the ability to get the proper cause is more important than saving the allocation. This will go out in next release (sometime this week) |
👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When getting the TimeoutException from hystrix command we can't trace it down to our specific code.
The issue seems to be that the TimeoutException created in the AbstractCommand (around line 600) is not chaining its cause.
I suggest to change the code from:
to something like this:
Thanks.
The text was updated successfully, but these errors were encountered: