[
https://issues.apache.org/jira/browse/CONNECTORS-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897876#comment-13897876
]
Karl Wright commented on CONNECTORS-880:
----------------------------------------
Hi Florian,
The version of SolrJ changed; it's now 4.6.0. Usually, though, SolrJ is pretty
backwards compatible, so I'm surprised that you are having difficulty with it,
but at the same time I can believe that they messed up over there. If you want
to rule out that cause, I think you can just replace the solr-solrj.jar in the
lib directory with the 4.3.1 equivalent, and rebuild.
I'll look at the trace over the next hour or so and see if it tells me anything
about the state issues. I did try this, FWIW, against localhost when Solr
wasn't even running, and saw nothing like this in the log.
> 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)
