[ 
https://issues.apache.org/jira/browse/CONNECTORS-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918460#action_12918460
 ] 

Karl Wright commented on CONNECTORS-111:
----------------------------------------

Looking at the complaint again:

Error: A lock could not be obtained due to a deadlock, cycle of locks and 
waiters is: 
Lock : ROW, INGESTSTATUS, (1,57) Waiting XID :6293, APP, DELETE FROM 
ingeststatus WHERE urihash=? AND dockey\!=? AND connectionname=? Granted XID 
:6305
Lock : ROW, INGESTSTATUS, (1,55) Waiting XID :6305, APP, INSERT INTO 
ingeststatus 
(id,changecount,dockey,lastversion,firstingest,connectionname,authorityname,urihash,lastoutputversion,lastingest,docuri)
 VALUES (?,?,?,?,?,?,?,?,?,?,?) Granted XID :6293

The selected victim is XID : 6293.

... it seems more like this has nothing to do with transactions, and more to do 
with an internal lock-ordering problem in Derby itself.  So, each database 
modification has a potential of throwing one of these exceptions.

I tried to fix that issue by retrying the operation should I be outside of a 
transaction.  r1004915.


> Encountering deadlock using quick-start & derby
> -----------------------------------------------
>
>                 Key: CONNECTORS-111
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-111
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Examples
>         Environment: Windows XP Professional SR3, Intel Core 2, 2 GB Ram
>            Reporter: Farzad
>
> Ran into problem with quick-start and thought I might have better luck if I 
> manually setup the system. Maybe you can shed a light on the quick-start 
> problem. Here is what happened, after running start.jar, I went to the 
> crawler UI, configured a null output and a file system repo connector. 
> Created a job pointing to a file share \\host\share and started the job. 
> After a few seconds I ran into the error message below in the job status 
> panel. It said 60 docs found, 9 active, and 52 processed. Any ideas as to why 
> I'm seeing this?
> Error: A lock could not be obtained due to a deadlock, cycle of locks and 
> waiters is: Lock : ROW, INGESTSTATUS, (1,57) Waiting XID : 
> Unknown macro: {6293, X} 
> , APP, DELETE FROM ingeststatus WHERE urihash=? AND dockey!=? AND 
> connectionname=? Granted XID : 
> Unknown macro: {6305, X} 
> Lock : ROW, INGESTSTATUS, (1,55) Waiting XID : 
> , APP, INSERT INTO ingeststatus 
> (id,changecount,dockey,lastversion,firstingest,connectionname,authorityname,urihash,lastoutputversion,lastingest,docuri)
>  VALUES (?,?,?,?,?,?,?,?,?,?,?) Granted XID : 
> . The selected victim is XID : 6293.
> Thanks!

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

Reply via email to