[
https://issues.apache.org/jira/browse/DERBY-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-6094:
--------------------------------------
Component/s: JDBC
> Derby ignores DriverManager.setLoginTimeout()
> ---------------------------------------------
>
> Key: DERBY-6094
> URL: https://issues.apache.org/jira/browse/DERBY-6094
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.10.1.1
> Reporter: Rick Hillegas
> Fix For: 10.10.1.1
>
> Attachments: Driver20.java, LoginTimeoutTest.java,
> LoginTimeoutTest.java, LoginTimeoutTest.java, LoginTimeoutTest.java,
> 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
>
>
> If you set a login timeout using the DriverManager, Derby ignores the
> setting. I will attach a test case which shows this.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
