[ 
https://issues.apache.org/jira/browse/DERBY-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kathey Marsden updated DERBY-3980:
----------------------------------

    Attachment: LiveLockTest_with_Deadlock_look_diff.txt

Here is the updated patch where I confirmed we enter Deadlock.look(). I made 
the sleep 25 seconds and used the default deadlock and wait timeouts.  I tried 
just adjusting the deadlock timeout down to achieve the same result, but found 
we were never entering Deadlock.look(). There seems to be a problem  with the 
timeout values at least when set low.


> Conflicting select then update with REPEATABLE_READ gives lock timeout 
> instead of deadlock
> ------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3980
>                 URL: https://issues.apache.org/jira/browse/DERBY-3980
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.3.0, 10.4.2.0, 10.5.0.0
>            Reporter: Kathey Marsden
>         Attachments: derby-3980_javadoc_and_test_diff.txt, derby.log, 
> derby.log.10_1, javacore.20081209.092827.9800.txt, LiveLockTest_diff.txt, 
> LiveLockTest_with_Deadlock_look_diff.txt, LockTimeoutWithInserts.java, 
> TryTimeout.java, TryTimeout2.java, TryTimeout2.out.10_1.deadlock, 
> TryTimeout2.out.10_1.deadlock, TryTimeout2.out.10_1.locktimeout, 
> TryTimeout2.out.10_1.locktimeout
>
>
> The attached program TryTimeout.java should detect a deadlock but instead 
> throws a lock timeout exception.  The program has two threads that attempt:
>           
>           threadConnection.setAutoCommit(false);
>           /* set isolation level to repeatable read */
>           
> threadConnection.setTransactionIsolation(Connection.TRANSACTION_REPEATABLE_READ);
>           
>           ResultSet rs = stmt.executeQuery("select * from t where i = 456");
>           while (rs.next());
>           stmt.executeUpdate("update t set i = 456 where i = 456");
>           threadConnection.commit();
> This gives SQLState 40001 (deadlock) with DB2 but a lock timeout with Derby.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to