db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <derby-...@db.apache.org>
Subject [jira] Resolved: (DERBY-715) lock deadlocks sometimes reported as lock timeouts
Date Fri, 02 Dec 2005 00:53:31 GMT
     [ http://issues.apache.org/jira/browse/DERBY-715?page=all ]
     
Mike Matrigali resolved DERBY-715:
----------------------------------

    Resolution: Fixed

submitted to trunk as revision 351543.

Sometimes (timing dependent) a lock deadlock was incorrectly returned to the
user as a lock timeout.  The code in LockSet was using the wrong variable
to determine if a deadlock had been detected, that variable sometimes was
right and sometimes wrong.  Changed all the code to use the direct return
from the deadlock detection routine.  Added a test that causes 5 deadlocks,
previous to the fix this test would always report at least 1 timeout on
my single processor, windows xp, laptop.

> lock deadlocks sometimes reported as lock timeouts
> --------------------------------------------------
>
>          Key: DERBY-715
>          URL: http://issues.apache.org/jira/browse/DERBY-715
>      Project: Derby
>         Type: Bug
>   Components: Services
>     Versions: 10.0.2.0
>     Reporter: Mike Matrigali
>     Assignee: Mike Matrigali
>     Priority: Minor
>      Fix For: 10.2.0.0
>  Attachments: repro.java
>
> Sometimes a lock deadlock is reported as a lock timeout, even when the software has done
a deadlock search and found it to be a deadlock.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message