[DERBY-6167] Interrupt restarts clock for login timeout

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.10.1.1
• Fix Version/s: 10.10.2.0, 10.11.1.1
• Component/s: JDBC
• Labels: derby_backport_reject_10_9 derby_triage10_11
• Urgency: Normal
• Issue & fix info: Repro attached
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 11/Apr/13 12:12
• Updated: 21/Jan/15 00:23
• Resolved: 09/Jul/13 10:51

Description

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.

Issue Links

• relates to: DERBY-6094 Derby ignores DriverManager.setLoginTimeout()