db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6094) Derby ignores DriverManager.setLoginTimeout()
Date Fri, 08 Mar 2013 17:40:13 GMT

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

Rick Hillegas updated DERBY-6094:

    Attachment: derby-6094-01-ad-enforceDriverManagerLoginTimeout.diff

Attaching derby-6094-01-ad-enforceDriverManagerLoginTimeout.diff. This version of the patch
beefs up LoginTimeoutTest with test cases from the repro. I'm running tests now. If the tests
pass, I plan to commit this version.

I'm still interested in the community's advice about how thread interrupts should interact
with login timeouts.

I've also looked into the failures in NativeAuthenticationServiceTest which appear when you
put it in a suite with another test and set derby.tests.login.timeout=10. I'm fairly certain
that this is a test design defect but I haven't gotten to the bottom of it yet.

Touches the following file:

M       java/testing/org/apache/derbyTesting/junit/JDBCClient.java

Made the DERBYNETCLIENT constant public so that LoginTimeoutTest can use it.

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