You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Alexander Kolbasov (JIRA)" <ji...@apache.org> on 2017/09/13 01:04:00 UTC

[jira] [Assigned] (SENTRY-1948) RetryClientInvocationHandler throws wrong exception up the stack

     [ https://issues.apache.org/jira/browse/SENTRY-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Kolbasov reassigned SENTRY-1948:
------------------------------------------

    Assignee:     (was: Alexander Kolbasov)

> RetryClientInvocationHandler throws wrong exception up the stack
> ----------------------------------------------------------------
>
>                 Key: SENTRY-1948
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1948
>             Project: Sentry
>          Issue Type: Bug
>          Components: Sentry
>    Affects Versions: 2.0.0
>            Reporter: Alexander Kolbasov
>
> RetryClientInvocationHandler.invokeImpl() does this:
> {code}
>       } catch (InvocationTargetException e) {
>         // Get the target exception, check if SentryUserException or TTransportException is wrapped.
>         // TTransportException means there is a connection problem.
>         LOGGER.error("failed to execute {}", method.getName(), e);
>         Throwable targetException = e.getCause();
>         if (!((targetException instanceof SentryUserException) ||
>             (targetException instanceof SentryHdfsServiceException))) {
>           throw e;   // <-- Here
>         }
> {code}
> So, instead of throwing the original exception it throws the InvocationTargetException.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)