You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sentry.apache.org by "Sravya Tirukkovalur (JIRA)" <ji...@apache.org> on 2014/06/12 21:53:02 UTC

[jira] [Updated] (SENTRY-296) Sentry Service Client does not allow for connection pooling

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

Sravya Tirukkovalur updated SENTRY-296:
---------------------------------------

    Labels: grant/revoke  (was: )

> Sentry Service Client does not allow for connection pooling
> -----------------------------------------------------------
>
>                 Key: SENTRY-296
>                 URL: https://issues.apache.org/jira/browse/SENTRY-296
>             Project: Sentry
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Lenni Kuff
>              Labels: grant/revoke
>
> The Sentry Service Client does not allow for connection pooling because there is no way to:
> 1) Detect that a connection is broken
> 2) Re-open a broken connection
> This would allow for Sentry Service clients to implement connection pooling like:
> {code}
> if (!client.isOpen()) {
>   client.reopen();
> }
> {code}
> Currently, the only way to ensure connections are not broken is to open a new connection before every RPC.



--
This message was sent by Atlassian JIRA
(v6.2#6252)