[DERBY-1696] transaction may sometimes keep lock on a row after moving off the resultset in scrollable updatable resultset

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.2.1.6, 10.2.2.0, 10.3.1.4
• Component/s: SQL, Store
• Labels: derby_triage10_5_2 derby_triage10_9
• Urgency: Normal
• Issue & fix info: Repro attached
• Assignee: Unassigned
• Reporter: Andreas Korneliussen
• Created: 15/Aug/06 14:05
• Updated: 21/Feb/12 07:44

Description

If an application does the following:

Statement s = con.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE,
ResultSet.CONCUR_UPDATABLE);
ResultSet rs = s.executeQuery("select * from t1");
rs.afterLast();
rs.last();
rs.next();

After doing this in transaction isolation level read-committed/read-uncommitted, the last row is still locked with an update lock.

This is detected by running the JUnit testcase ConcurrencyTest.testUpdatePurgedTuple1 in the DerbyNetClient framework.
(NOTE: the bug is revealed by this test, because the network server does a rs.last() as the first operation on a scrollable updatable resultset to count number of rows)

What triggers this bug, seems to be the repositioning of the cursor after the underlying all records have been inserted into the hashtable from the source scan. When moving off the result set (to afterLast() or beforeFirst()) no action is done to release the lock of the current row.

Issue Links

• is related to: DERBY-1799 SUR: current row not locked when renavigating to it, in queries with indexes