[ 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