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
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