[
https://issues.apache.org/jira/browse/DERBY-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas resolved DERBY-6094.
----------------------------------
Resolution: Fixed
Fix Version/s: 10.10.0.0
I believe the work on this issue is done. I have logged a follow-on issue,
DERBY-6107, to investigate why setting a login timeout causes
NativeAuthenticationServiceTest to fail when run inside a larger suite.
> 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
> Fix For: 10.10.0.0
>
> 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, derby-6094-03-aa-retryOnInterrupt.diff,
> derby-6094-04-aa-testCleanup.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
