[
https://issues.apache.org/jira/browse/CONNECTORS-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896778#comment-13896778
]
Florian Schmedding commented on CONNECTORS-880:
-----------------------------------------------
I installed mcf-combined-service.war version 1.6 on a Tomcat server. However,
the test job is not working correctly. I've used an existing database from
Manifold 1.3 with one existing output connection, one existing repository
connection and one existing job. On the job status page there were no buttons
to control the job, its status is "End notification". Therefore I copied the
job. Then there were buttons to start the new job, but it got only errors from
the output connection when ingesting documents. After aborting the job, it got
stuck with the status "End notification" and does not leave it. Should I better
create new connections and jobs or are there other problems in version 1.6?
> 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)
