[ 
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-02-aa-createDBFirst.diff

Attaching derby-6094-02-aa-createDBFirst.diff. Hopefully, this will fix the 
failure in LoginTimeoutTest seen on Linux. Committed at subversion revision 
1455156.

I ran the LoginTimeoutTest on Java 7 on Linux running inside VirtualBox on Mac 
OSX. The test failed for me there. For some reason, database creation takes a 
long time in that environment. This caused an initial connection attempt to 
fail on a login timeout when the test expected the connection attempt to 
succeed. I have changed the test in order to remove this source of heisenbugs. 
Now the test creates the database before trying to test timeouts.

While I was in there, I also added some more defensive logic to make the test 
cleanup after itself when an unexpected error occurs.

Touches the following files:

M       
java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/LoginTimeoutTest.java
M       java/testing/org/apache/derbyTesting/junit/BaseTestCase.java

                
> Derby ignores DriverManager.setLoginTimeout()
> ---------------------------------------------
>
>                 Key: DERBY-6094
>                 URL: https://issues.apache.org/jira/browse/DERBY-6094
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.10.0.0
>            Reporter: Rick Hillegas
>         Attachments: derby-6094-01-ac-enforceDriverManagerLoginTimeout.diff, 
> derby-6094-01-ad-enforceDriverManagerLoginTimeout.diff, 
> derby-6094-01-ae-enforceDriverManagerLoginTimeout.diff, 
> derby-6094-02-aa-createDBFirst.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

Reply via email to