[
https://issues.apache.org/jira/browse/DERBY-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598177#comment-13598177
]
Knut Anders Hatlen commented on DERBY-6094:
-------------------------------------------
The new test failed in the latest nightly test cycle:
http://download.java.net/javadesktop/derby/javadb-5573775-report/javadb-5573775-3606706-details.html
junit.framework.AssertionFailedError: Should have been able to connect!
at
org.apache.derbyTesting.functionTests.tests.jdbc4.LoginTimeoutTest.tryTimeout(LoginTimeoutTest.java:290)
at
org.apache.derbyTesting.functionTests.tests.jdbc4.LoginTimeoutTest.tryTimeout(LoginTimeoutTest.java:277)
at
org.apache.derbyTesting.functionTests.tests.jdbc4.LoginTimeoutTest.vetConnector(LoginTimeoutTest.java:266)
at
org.apache.derbyTesting.functionTests.tests.jdbc4.LoginTimeoutTest.testBasic(LoginTimeoutTest.java:255)
at
org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:117)
(...)
> 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,
> 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
