[
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-03-aa-retryOnInterrupt.diff
Attaching derby-6094-03-aa-retryOnInterrupt.diff. This patch applies Dag's
suggested changes. I am running tests now.
I also added a login timeout to the InterruptResilienceTest. That forces the
new logic to be excercised.
With the new logic, I have successfully run InterruptResilienceTest and
LoginTimeoutTest on Mac OSX and on Linux on top of VirtualBox on top of Mac OSX.
Touches the following files:
M java/engine/org/apache/derby/jdbc/Driver20.java
M
java/testing/org/apache/derbyTesting/functionTests/tests/store/InterruptResilienceTest.java
> 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
