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

["Mayur (JIRA)" <ji...@apache.org>]

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

Mayur commented on DERBY-6970:
------------------------------

Hi Bryan,

We aren't getting any exceptions, our concern is just that when we are trying to set the connection time-out parameter to n number of seconds,  it is taking 5 seconds by default for any parameter we assigned. We tried the following by using
 "derbyclient-10.13.1.1.jar" with client server mode communication like,
ClientDataSource ds = new ClientDataSource();
ds.setLoginTimeout(15) / ds.setLoginTimeout(25) / ds.setLoginTimeout(2) and so on.

So here as per the parameters connection time-out exception should have come after 15/25/2 seconds respectively. But for each and every parameter its taking 5 sec by default.
Please help us out if you have any solution to the above issue. Its really affecting our performance request you to kindly respond quickly.

Thank you
Mayur


> 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, 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)