Retry on HTTP Status code (eg: 429, 500, 502, 503, 504) in Helidon REST API about helidon

[spericas]

There's one way to support a similar use case using existing features in Rest Client and Fault Tolerance. Rest Client has the notion of a ResponseExceptionMapper, which can be used to map a Response to an Exception. For example,

    public class MyResponseMapper implements ResponseExceptionMapper<MyException> {

        @Override
        public MyException toThrowable(Response response) {
            if (response.getStatus() != 200) {
                System.out.println("Throwing exception");
                throw new MyException(response.getStatus());
            }
            return null;
        }
    }

In this example, and mainly for simplicity, any status code other than 200 is mapped to an instance of MyException (naturally, different error codes could be mapped to different exception types). This mapper can be registered as a provider in a client and used with the normal FT @Retry:

    @Path("/greet")
    @RegisterRestClient(baseUri="http://localhost:8080")
    @RegisterProvider(MyResponseMapper.class)
    public interface GreetResourceClient {

        @GET
        @Retry(retryOn = { MyException.class })
        @Produces(MediaType.APPLICATION_JSON)
        Response getDefaultMessage();
    }

Thus, any time MyException is thrown, the exception will be caught by the FT handler and the method retried up to 3 times (the default for that annotation).

I understand this may not be as convenient as having a dedicated annotation for this purpose, but it is possible using existing constructs and extensions.

[spericas]

@sammee Have you tried the proposed alternative?

[sammee]

@spericas I have implemented a variant of this. Using ResponseMapper will throw a custom exception for a particular status code. This will be applied for all Rest clients. Instead, I wanted to have retry on some specific api. So i have used @Retry annotation on the method where the api is called and throw a custom exception when the status-code or error is retryable.
Thanks for the suggestion.

[spericas]

I gather from the comments that the workaround or alternative is satisfactory. Closing as won't fix for now.