[
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-01-ae-enforceDriverManagerLoginTimeout.diff
Attaching derby-6094-01-ae-enforceDriverManagerLoginTimeout.diff. This third
rev of the patch changes LoginTimeoutTest to use the singleUseDatabaseDecorator
rather than CleanDatabaseTestSetup. For some reason, CleanDatabaseTestSetup
results in errors when LoginTimeoutTest is run in a suite alongside other JUnit
tests. Re-running the JUnit tests...
> 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
