Return-Path: X-Original-To: apmail-manifoldcf-dev-archive@www.apache.org Delivered-To: apmail-manifoldcf-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B32B117672 for ; Thu, 4 Jun 2015 23:40:39 +0000 (UTC) Received: (qmail 47795 invoked by uid 500); 4 Jun 2015 23:40:39 -0000 Delivered-To: apmail-manifoldcf-dev-archive@manifoldcf.apache.org Received: (qmail 47753 invoked by uid 500); 4 Jun 2015 23:40:39 -0000 Mailing-List: contact dev-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@manifoldcf.apache.org Delivered-To: mailing list dev@manifoldcf.apache.org Received: (qmail 47645 invoked by uid 99); 4 Jun 2015 23:40:39 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Jun 2015 23:40:39 +0000 Date: Thu, 4 Jun 2015 23:40:39 +0000 (UTC) From: "Karl Wright (JIRA)" To: dev@manifoldcf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CONNECTORS-1191) ManifoldCFException: Unexpected job status encountered MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CONNECTORS-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573817#comment-14573817 ] Karl Wright commented on CONNECTORS-1191: ----------------------------------------- bq. BTW: Some jobs (see screenshot) have status "Waiting" ... I wonder what that means. Waiting just means it is outside the scheduling window. bq. Is it possible that another instance of the jobs is scheduled while one is already running? No, because jobs don't run that way; they're either active or not. bq. This clearly shows that we have thread 99 and 82 processing the very same document. So, in order for this to happen, the stuffer thread has to pick up the document twice. The stuffer thread finds documents and then sets their state to "active" so that they cannot be picked up a second time. But clearly that's not working properly on your setup. That is consistent with what I've seen before with some versions of MySQL: you can write to the database all you like and once in a while the write says it happened but a later read does not see that last-written result. It's a transactional integrity problem. I don't know why it is affecting you so strongly, but it clearly is happening a lot on your system. > ManifoldCFException: Unexpected job status encountered > ------------------------------------------------------ > > Key: CONNECTORS-1191 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1191 > Project: ManifoldCF > Issue Type: Bug > Components: Web connector > Affects Versions: ManifoldCF 2.0.2 > Environment: - Debian 7.8 x86_64 GNU/Linux > - Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed mode) > - Server version: 5.5.41-0+wheezy1 (Debian) > Reporter: Arcadius Ahouansou > Assignee: Karl Wright > Priority: Critical > Fix For: ManifoldCF 1.9, ManifoldCF 2.1 > > Attachments: 1433374857580-jobs.png, 1433374857580-schedule.png, CONNECTORS-1191-2.patch, CONNECTORS-1191.patch, manifoldcf2.0.2.log, stuffer-thread-manifoldcf.log, unexpected-jobqueue.png > > > Hello. > I am running the latest ManifoldCF 2.0.2 and my log is filled of > {code} > org.apache.manifoldcf.core.interfaces.ManifoldCFException: Unexpected job status encountered: 34 > at org.apache.manifoldcf.crawler.jobs.Jobs.returnJobToActive(Jobs.java:2073) > at org.apache.manifoldcf.crawler.jobs.JobManager.resetJobs(JobManager.java:8261) > at org.apache.manifoldcf.crawler.system.JobResetThread.run(JobResetThread.java:91) > {code} > I have attached full log for more detail. > Note that I am running against MySQL. > Thanks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)