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

Karl Wright commented on CONNECTORS-590:
----------------------------------------

The only hypothesis that may make some sense is that we're seeing a "reset" due 
to either an unhandled database exception, or due to an error condition.  The 
bug would be that the reset gets applied not only to documents that actually 
failed, but also to documents that had been already handed to active worker 
threads.  I would expect there to be some kind of log warning if this took 
place however, within the last 10 minutes of the crawl before the bad state was 
seen.

                
> ManifoldCF sometimes throws an unexpected state exception under MySQL
> ---------------------------------------------------------------------
>
>                 Key: CONNECTORS-590
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-590
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Framework core
>    Affects Versions: ManifoldCF 1.0.1, ManifoldCF 1.1
>         Environment: MySQL 5.5.28, for Linux (x86_64), ManifoldCF 1.1-dev
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 1.1
>
>
> The following exception occurred under this setup:
> {code}
> 2012/12/21 10:09:37 ERROR (Worker thread '78') - Exception tossed: Unexpected 
> jobqueue status - record id 1356045273314, expecting active status, saw 0
> org.apache.manifoldcf.core.interfaces.ManifoldCFException: Unexpected 
> jobqueue status - record id 1356045273314, expecting active status, saw 0
>         at 
> org.apache.manifoldcf.crawler.jobs.JobQueue.updateCompletedRecord(JobQueue.java:742)
>         at 
> org.apache.manifoldcf.crawler.jobs.JobManager.markDocumentCompletedMultiple(JobManager.java:2438)
>         at 
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:765)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to