Ah, it's actually much simpler than I thought.
ConnectTimeoutException wraps SocketTimeoutExceptions
but you use ExceptionUtils.getRootCause which retrieves the inner most
exception - which is SocketTimeoutException
so
1. logging or posting a full stackrace would make the reason obvious from
the b
On Wed, Feb 12, 2020 at 9:33 AM Alexey Panchenko
wrote:
> Ah, it's actually much simpler than I thought.
> ConnectTimeoutException wraps SocketTimeoutExceptions
> but you use ExceptionUtils.getRootCause which retrieves the inner most
> exception - which is SocketTimeoutException
>
> so
> 1. loggi
Evan,
> I can do an ugly hack to look for a cause, and if it matches connection
> timeout, pull it from the immediate cause; otherwise, grab the root cause
> to handle others (there are other custom exceptions that are wrapped by
> RestClientException, hence the reason).
>
I think just using getCa
