[DERBY-4863] Derby update operation with setQueryTimeout does not timeout until the locks are released.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.6.2.1
• Component/s: JDBC
• Labels: derby_triage10_8
• Environment: windows 7, jdk 1.5.0_22, derby 10.6.2.1
• Urgency: Low
• Issue & fix info: Repro attached
• Bug behavior facts: Deviation from standard
• Assignee: Unassigned
• Reporter: Florin Herinean
• Created: 21/Oct/10 10:26
• Updated: 29/Sep/16 23:46

Description

Derby update statements do not timeout until the (write) locks are released.

The scenario involves 2 threads starting 2 separate transactions/connections, each of them attempting to update the same row. The first thread starts the transaction, locks the row (via update) then waits 40 seconds. The second thread is started 5 seconds later and it has a 5 seconds timeout set on the statement. Upon attempting to update the same row as the first thread, it times out after 35 seconds (40 - 5) and not after the expected 5 seconds as specified in the statement timeout.

A test case is attached.

Oracle and DB2 behaves as expected.