db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6094) Derby ignores DriverManager.setLoginTimeout()
Date Sun, 10 Mar 2013 11:09:12 GMT

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

Dag H. Wanvik updated DERBY-6094:

    Attachment: Driver20.java

Uploading a modified Driver20.java suggesting how we could handle interrupts seen in the util.concurrent
calls. Basically, the code retries the connect until the timeout has happened or success,
reestablish the interrupt flag on exit. This also makes InterruptResilienceTest work in my
> Derby ignores DriverManager.setLoginTimeout()
> ---------------------------------------------
>                 Key: DERBY-6094
>                 URL: https://issues.apache.org/jira/browse/DERBY-6094
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions:
>            Reporter: Rick Hillegas
>         Attachments: derby-6094-01-ac-enforceDriverManagerLoginTimeout.diff, derby-6094-01-ad-enforceDriverManagerLoginTimeout.diff,
derby-6094-01-ae-enforceDriverManagerLoginTimeout.diff, Driver20.java, LoginTimeoutTest.java,
LoginTimeoutTest.java, LoginTimeoutTest.java, LoginTimeoutTest.java
> If you set a login timeout using the DriverManager, Derby ignores the setting. I will
attach a test case which shows this.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message