db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Florin Herinean (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-4863) Derby update operation does not timeout until the locks are released.
Date Thu, 21 Oct 2010 10:27:15 GMT
Derby update operation does not timeout until the locks are released.
---------------------------------------------------------------------

                 Key: DERBY-4863
                 URL: https://issues.apache.org/jira/browse/DERBY-4863
             Project: Derby
          Issue Type: Bug
          Components: Network Server
    Affects Versions: 10.6.2.1
         Environment: windows 7, jdk 1.5.0_22, derby 10.6.2.1
            Reporter: Florin Herinean


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.

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


Mime
View raw message