You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mike Matrigali (JIRA)" <de...@db.apache.org> on 2005/11/18 01:09:45 UTC
[jira] Created: (DERBY-715) lock deadlocks sometimes reported as lock timeouts
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
Assigned to: Mike Matrigali
Priority: Minor
Fix For: 10.2.0.0
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
[jira] Resolved: (DERBY-715) lock deadlocks sometimes reported as lock timeouts
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Updated: (DERBY-715) lock deadlocks sometimes reported as lock timeouts
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-715?page=all ]
Mike Matrigali updated DERBY-715:
---------------------------------
Attachment: derby715.diff
I have not run tests on this diff yet, just posting to get some input on whether I am on the right track or not. Do not commit this patch until I have had a chance to get it reviewed and run tests.
> 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: derby715.diff, 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
[jira] Resolved: (DERBY-715) lock deadlocks sometimes reported as lock timeouts
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-715?page=all ]
Mike Matrigali resolved DERBY-715:
----------------------------------
Fix Version: 10.1.3.0
Resolution: Fixed
svn 353812 ports fix from trunk to 10.1
> 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, 10.1.3.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
[jira] Closed: (DERBY-715) lock deadlocks sometimes reported as
lock timeouts
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-715?page=all ]
Mike Matrigali closed DERBY-715:
--------------------------------
> 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, 10.1.3.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
[jira] Updated: (DERBY-715) lock deadlocks sometimes reported as lock timeouts
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-715?page=all ]
Mike Matrigali updated DERBY-715:
---------------------------------
Attachment: (was: derby715.diff)
> 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
[jira] Updated: (DERBY-715) lock deadlocks sometimes reported as lock timeouts
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-715?page=all ]
Mike Matrigali updated DERBY-715:
---------------------------------
Attachment: repro.java
slightly altered repro from the one bryan posted to DERBY-666, mostly just some extra prints.
On my ~2 ghz single processor laptop, running windows and jdk1.4.2 when I run the test the
first time I get a deadlock, and then mostly get timeouts reported for subsequent runs.
Note that the first time there are 0 rows in the table, but after each iteration there are some
committed deleted rows which changes the internal timing - to the user since the test never
commits there are always no rows in the tables.
It is
clear that the time to the timeout is the deadlock time - NOT the timeout time.
> 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
[jira] Reopened: (DERBY-715) lock deadlocks sometimes reported as lock timeouts
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-715?page=all ]
Mike Matrigali reopened DERBY-715:
----------------------------------
> 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, 10.1.3.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