[
https://issues.apache.org/jira/browse/DERBY-6167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen resolved DERBY-6167.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.11.0.0
10.10.1.3
> Interrupt restarts clock for login timeout
> ------------------------------------------
>
> Key: DERBY-6167
> URL: https://issues.apache.org/jira/browse/DERBY-6167
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.10.1.1
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Priority: Minor
> Labels: derby_triage10_11
> Fix For: 10.10.1.3, 10.11.0.0
>
> Attachments: derby-6167-1a.diff, InterruptDuringConnect.java
>
>
> If a login takes time, and the thread that's blocked in Driver20.timeLogin()
> is interrupted, it will call Future.get() again with the same timeout value.
> This means that interrupting a getConnection() call will not make it
> terminate faster, as one might expect. Instead, it restarts the timeout clock
> and makes it terminate later than if it had not been interrupted.
--
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
