[
https://issues.apache.org/jira/browse/CONNECTORS-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898011#comment-13898011
]
Karl Wright edited comment on CONNECTORS-880 at 2/11/14 5:06 PM:
-----------------------------------------------------------------
Hi Florian,
There is no magic here. Something cannot be correctly configured. The Solr
connector is used extensively, and there are mock tests for it as well.
My suggestion is to capture the back-and-forth between MCF and your Solr
instance using a tool like WireShark. See what the critical factor is.
was (Author: [email protected]):
Hi Florian,
There is no magic here. Something cannot be correctly configured. The Solr
connector is used extensively, and there are mock tests for it as well.
> 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)
