You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2017/10/17 02:21:00 UTC

[jira] [Commented] (DERBY-6970) No support for setting connection timeout for a connection

    [ https://issues.apache.org/jira/browse/DERBY-6970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16206918#comment-16206918 ] 

Rick Hillegas commented on DERBY-6970:
--------------------------------------

See the attached DERBY_6970 program for an example of how to set a login timeout on a Derby DataSource. If this example does not work for you, then please post the error message you are seeing along with the contents of derby.log.

Thanks,
-Rick

> No support for setting connection timeout for a connection
> ----------------------------------------------------------
>
>                 Key: DERBY-6970
>                 URL: https://issues.apache.org/jira/browse/DERBY-6970
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>    Affects Versions: 10.13.1.1
>         Environment: Linux Operating system Resin App server
>            Reporter: Satyabrata Mohanty
>         Attachments: DERBY_6970.java
>
>
> https://stackoverflow.com/questions/44722659/providing-connection-time-out-in-derby-client-driver
> This is the link where i have put the details of my requirement. Basically my question is, how we can provide a timeout to connection, if connection object not established within that specific time it must get out from infinite waiting and resulting any exception or null, but seems to be there is no such functionality in derby till now. Request you to kindly look-into this and provide your inputs like if there is a way to achieve this then mention it with clear steps  or else if its not implemented then when we can get this must have required feature in derby. Its really affecting our performance request you to kindly respond quickly.
> Thanks!



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