You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by "Farzad (JIRA)" <ji...@apache.org> on 2010/10/05 20:50:33 UTC
[jira] Created: (CONNECTORS-111) Encountering deadlock using
quick-start & derby
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.
[jira] Resolved: (CONNECTORS-111) Encountering deadlock using
quick-start & derby
Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONNECTORS-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Wright resolved CONNECTORS-111.
------------------------------------
Resolution: Fixed
Fix Version/s: LCF Release 0.5
Retry seems to have fixed things.
> 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
> Assignee: Karl Wright
> Fix For: LCF Release 0.5
>
>
> 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.
[jira] Commented: (CONNECTORS-111) Encountering deadlock using
quick-start & derby
Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONNECTORS-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918134#action_12918134 ]
Karl Wright commented on CONNECTORS-111:
----------------------------------------
I made a change that should make the derby ManifoldCF database implementation more robust against exceptions thrown during commit or rollback. r1004786. See if this makes any difference in your setup.
> 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.
[jira] Commented: (CONNECTORS-111) Encountering deadlock using
quick-start & derby
Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONNECTORS-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918121#action_12918121 ]
Karl Wright commented on CONNECTORS-111:
----------------------------------------
As discussed in Confluence, the code in question is not apparently within a database transaction, so it's puzzling to me how a deadlock could develop. The possibilities are:
(1) Derby detects deadlocks in part by timeout. Perhaps the derby timeout time is too short.
(2) It could be a plain old Derby bug.
(3) There could be an error occuring at some point earlier during connection.commit(), which is confusing the ManifoldCF derby implementation. The semantics of such errors are not clear. I suppose I can presume that a rollback took place in that case.
> 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.
[jira] Commented: (CONNECTORS-111) Encountering deadlock using
quick-start & derby
Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CONNECTORS-111) Encountering deadlock using
quick-start & derby
Posted by "Farzad (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONNECTORS-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918507#action_12918507 ]
Farzad commented on CONNECTORS-111:
-----------------------------------
I tried your fix this morning and I was able to run the job successfully the first time after setup. Seems to be resolved. I ran a few other experiments and they were fine too. Thanks!
> 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.
[jira] Commented: (CONNECTORS-111) Encountering deadlock using
quick-start & derby
Posted by "Farzad (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONNECTORS-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918119#action_12918119 ]
Farzad commented on CONNECTORS-111:
-----------------------------------
I experimented more and it seems to be happening the first time after a clean setup of ManifoldCF. Subsequent jobs including the same job ran successfully.
> 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.
[jira] Assigned: (CONNECTORS-111) Encountering deadlock using
quick-start & derby
Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CONNECTORS-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Wright reassigned CONNECTORS-111:
--------------------------------------
Assignee: Karl Wright
> 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
> Assignee: Karl Wright
> Fix For: LCF Release 0.5
>
>
> 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.