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] [Comment Edited] (CONNECTORS-880) Under the right conditions, job aborts do not update "last checked" time
Date Wed, 12 Feb 2014 16:56:20 GMT

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

Florian Schmedding edited comment on CONNECTORS-880 at 2/12/14 4:55 PM:
------------------------------------------------------------------------

I believe that in my case the job repetition was depending on the wrong collation. When running
a job with a case-insensitive collation in MySQL it get started again without a previous job
end. The same job runs as expected with a correctly configured database. However, I think
your fix does not intend to remedy completely inconsistent status values resulting from the
wrong collation. So my setup isn't a test case for it.


was (Author: florianschmedding):
I believe that in my case the job repetition was depending on the wrong collation. When running
a job with a case-insensitive collation in MySQL it get started again without a previous job
end. The same job runs as expected with a correctly configured database. However, I think
your fix does not intend to remedy completely inconsistent status values resulting from the
wrong collation. So my setup inn't a test case for it.

> 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