You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
TimeoutExceptiontimeoutException = newTimeoutException();
timeoutException.initCause(t); // IMPORTANT - chaining to the causereturngetFallbackOrThrowException(HystrixEventType.TIMEOUT, FailureType.TIMEOUT, "timed-out", timeoutException);
Thanks.
The text was updated successfully, but these errors were encountered:
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)
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: