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

Rick Hillegas updated DERBY-6970:
---------------------------------
    Attachment: DERBY_6970.java

Attaching DERBY_6970.java. This is a test program which demonstrates that 
ClientDataSource.setLoginTimeout() works correctly. The program sets a 5 second 
login timeout on the data source. I tested the program by compiling the Derby 
engine with a 10 second delay added to the creation of an EmbedConnection. Then 
I brought up a network server and ran the program. As expected, the program 
printed:

   Login timeout exceeded.

This functionality is tested by LoginTimeoutTest every time that someone runs 
the full regression tests.


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

Reply via email to