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
we have ReactiveRectryPolicy (Basic/Filtered). Whenever retries are exhausted, it wraps the original exception with OutOfRetriesException.
How can I unwrap it?
Is there any handler available which can map it to my custom exception. For Example, We have ErrorDecoder, in which based on the http exception, I can map it to my custom exception. But this is only intercepted for http request. Which basically executes after each retry. And after all the retries, It executes the onErrorResume <- wrapWithOutOfRetriesLog <- RetryPublisherHttpClient. Which I can't intercept.
So, is there any way where I can convert OutOfRetriesException to my custom exception?
we have ReactiveRectryPolicy (Basic/Filtered). Whenever retries are exhausted, it wraps the original exception with OutOfRetriesException.
How can I unwrap it?
Is there any handler available which can map it to my custom exception. For Example, We have ErrorDecoder, in which based on the http exception, I can map it to my custom exception. But this is only intercepted for http request. Which basically executes after each retry. And after all the retries, It executes the
onErrorResume <- wrapWithOutOfRetriesLog <- RetryPublisherHttpClient
. Which I can't intercept.So, is there any way where I can convert OutOfRetriesException to my custom exception?
@kptfh
The text was updated successfully, but these errors were encountered: