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
ah ok, thanks :)
but then currently no way to make a stateless retry throw an ExhaustedRetryException by default, right?
in some cases it would be useful to be able to distinguish that cause from the original exceptions - but if thats really needed the wrapping can be handled manually in a recoverer as well, i guess...
this is maybe more a question than a real issue but i would like to know what is the expected behavior.
the readme states that
but for a stateless retry, that is not the behavior i am seeing (always original exception thrown).
handleRetryExhausted
is invoked correctly, withstate
beingnull
(ok, i guess, because the retry is stateless). but then, it looks like always the original exception is thrown back to the user, never wrapped in anExhaustedRetryException
. that is becausethrown()
is not invoked but instead justthrow wrapIfNecessary(context.getLastThrowable());
(https://github.com/spring-projects/spring-retry/blob/master/src/main/java/org/springframework/retry/support/RetryTemplate.java#L467)thanks for clarification!
The text was updated successfully, but these errors were encountered: