[jira] Created: (DERBY-3980) Conflicting select then update with REPEATABLE_READ gives lock timeout instead of deadlock

[Kathey Marsden (JIRA)]

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.4.2.0, 10.3.3.0, 10.2.2.0, 10.1.3.1, 10.5.0.0
            Reporter: Kathey Marsden
         Attachments: derby.log, TryTimeout.java

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.