manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Florian Schmedding (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONNECTORS-880) Under the right conditions, job aborts do not update "last checked" time
Date Tue, 11 Feb 2014 09:31:19 GMT

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

Florian Schmedding commented on CONNECTORS-880:
-----------------------------------------------

There are some error in the manifold log:

DEBUG 2014-02-11 10:11:11,989 (Thread-20602) - Actual query: [SELECT status,connectionname,outputname
FROM jobs WHERE id=? FOR UPDATE]
DEBUG 2014-02-11 10:11:11,989 (Thread-20602) -   Parameter 0: '1392051994515'
DEBUG 2014-02-11 10:11:11,989 (Thread-20602) - Done actual query (0ms): [SELECT status,connectionname,outputname
FROM jobs WHERE id=? FOR UPDATE]
DEBUG 2014-02-11 10:11:11,989 (Job reset thread) - Ending transaction
DEBUG 2014-02-11 10:11:11,989 (Job reset thread) - Rolling transaction back!
DEBUG 2014-02-11 10:11:11,992 (Thread-20603) - Actual query: [ROLLBACK]
DEBUG 2014-02-11 10:11:11,992 (Thread-20603) - Done actual query (0ms): [ROLLBACK]
ERROR 2014-02-11 10:11:11,992 (Job reset thread) - Exception tossed: Unexpected job status
encountered: 33
org.apache.manifoldcf.core.interfaces.ManifoldCFException: Unexpected job status encountered:
33
	at org.apache.manifoldcf.crawler.jobs.Jobs.returnJobToActive(Jobs.java:1726)
	at org.apache.manifoldcf.crawler.jobs.JobManager.resetJobs(JobManager.java:7427)
	at org.apache.manifoldcf.crawler.system.JobResetThread.run(JobResetThread.java:91)

There is a similar exception with "Unexpected job status encountered: 34". When looking into
the database, the status field of all jobs is constantly changing between 's' and 'n'.

> Under the right conditions, job aborts do not update "last checked" time
> ------------------------------------------------------------------------
>
>                 Key: CONNECTORS-880
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-880
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Framework crawler agent
>    Affects Versions: ManifoldCF 1.4.1
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 1.6
>
>
> When a scheduled job is being considered to be started, MCF updates the last-check field
ONLY if the job didn't start.  It relies on the job's completion to set the last-check field
in the case where the job does start.  But if the job aborts, in at least one case the last-check
field is NOT updated.  This leads to the job being run over and over again within the schedule
window.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message