[DERBY-5073] Derby deadlocks without recourse on simultaneous correlated subqueries

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 10.0.2.1, 10.1.2.1, 10.2.2.0, 10.3.3.0, 10.4.2.0, 10.5.3.0, 10.6.2.1, 10.7.1.1, 10.8.1.2
• Component/s: Services
• Issue & fix info: Repro attached
• Bug behavior facts: Performance, Seen in production
• Assignee: Knut Anders Hatlen
• Reporter: Karl Wright
• Created: 27/Feb/11 16:31
• Updated: 17/Jun/13 09:19
• Resolved: 23/Mar/11 12:27

Description

When the following two queries are run against tables that contain the necessary fields, using multiple threads, Derby deadlocks and none of the queries ever returns. Derby apparently detects no deadlock condition, either.

SELECT t0.* FROM jobqueue t0 WHERE EXISTS(SELECT 'x' FROM carrydown t1 WHERE t1.parentidhash IN AND t1.childidhash=t0.dochash AND t0.jobid=t1.jobid) AND t0.jobid=?
SELECT t0.* FROM jobqueue t0 WHERE EXISTS(SELECT 'x' FROM carrydown t1 WHERE t1.parentidhash IN AND t1.childidhash=t0.dochash AND t0.jobid=t1.jobid AND t1.newField=?) AND t0.jobid=?

This code comes from Apache ManifoldCF, and has occurred when there are five or more threads trying to execute these two queries at the same time. Originally we found this on 10.5.3.0. It was hoped that 10.7.1.1 would fix the problem, but it hasn't.

Issue Links

• blocks: CONNECTORS-166 Crawl seizes up when running Derby
• duplicates: DERBY-3980 Conflicting select then update with REPEATABLE_READ gives lock timeout instead of deadlock
• is related to: DERBY-2877 Print the entire lock list when a deadlock occurs and deadlock tracing is on