[
https://issues.apache.org/jira/browse/CONNECTORS-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897969#comment-13897969
]
Florian Schmedding commented on CONNECTORS-880:
-----------------------------------------------
OK, now all jobs are finished. I disabled the option "Commit at end of every
job" for the Solr connection (and additionally didn't start Solr). When this
option is enabled the above IO exception is still there even if Solr is not
running. The job states are now:
Done (for the job that remained from the previous Manifold version used)
Error: Repeated service interruptions during notification: The target server
failed to respond (a copy of the previous job generated with version 1.6)
Error: Repeated service interruptions - failure processing document: The target
server failed to respond (a job created with version 1.6)
However, after restarting Tomcat, there are still two of the unexpected job
status encountered exceptions (33 and 34). It looks like they belong to the job
that was remaining from the previous Manifold version I used.
I'm using MySQL version 5.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)
