You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2014/12/11 00:22:13 UTC

[jira] [Updated] (CALCITE-524) Connection timeout and keep-alive in remote JDBC driver

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

Julian Hyde updated CALCITE-524:
--------------------------------
    Description: 
Implement a timeout policy, whereby a connection that is inactive for a given period is closed.

Also implement a way for the remote JDBC client to tell the server that the connection is still in use.

Test that executing an operation, say createStatement, on a connection that has been closed server-side gives a good error from JDBC client, and that the connection's state is then set to closed (per Connection.isClosed).

Also, document how keep-alive works in the documentation produced by CALCITE-517.

  was:
Implement a timeout policy, whereby a connection that is inactive for a given period is closed.

Also implement a way for the remote JDBC client to tell the server that the connection is still in use.

Test that executing an operation, say createStatement, on a connection that has been closed server-side gives a good error from JDBC client, and that the connection's state is then set to closed (per Connection.isClosed).


> Connection timeout and keep-alive in remote JDBC driver
> -------------------------------------------------------
>
>                 Key: CALCITE-524
>                 URL: https://issues.apache.org/jira/browse/CALCITE-524
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>
> Implement a timeout policy, whereby a connection that is inactive for a given period is closed.
> Also implement a way for the remote JDBC client to tell the server that the connection is still in use.
> Test that executing an operation, say createStatement, on a connection that has been closed server-side gives a good error from JDBC client, and that the connection's state is then set to closed (per Connection.isClosed).
> Also, document how keep-alive works in the documentation produced by CALCITE-517.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)