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, 01 Mar 2013 20:09: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: LoginTimeoutTest.java

Attaching a new version of LoginTimeoutTest. This version shows what Derby does in the following

1) An embedded app tries to connect after calling DriverManager.setLoginTimeout() on the embedded

2) A client app tries to connect after someone called DriverManager.setLoginTimeout() on the
server VM.

3) A client app tries to connect after calling DriverManager.setLoginTimeout() on the client

I believe that in all 3 situations, sluggish logins should result in java.sql.SQLTimeoutException.
The behavior right now is:

(1) and (2): no exception

(3): a java.sql.SQLNonTransientConnectionException

I have coded a candidate solution, but I want to run a battery of tests before submitting
it for community review.

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