[
https://issues.apache.org/jira/browse/DERBY-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598948#comment-13598948
]
Knut Anders Hatlen commented on DERBY-6094:
-------------------------------------------
Thanks for fixing the test instability, Rick.
Two small nits:
- The new connection that's used to ensure the database is created, should
probably be closed after use (connections created with openDefaultConnection()
aren't automatically closed by the framework).
- The new minion failWithTrace() duplicates the functionality in
BaseTestCase.fail(String msg, Throwable t), except the latter will make the
original stack trace available to the JUnit machinery, not just print it to the
console.
> 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, derby-6094-03-aa-retryOnInterrupt.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
