[
https://issues.apache.org/jira/browse/CONNECTORS-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898337#comment-13898337
]
Florian Schmedding commented on CONNECTORS-880:
-----------------------------------------------
Yes, I did replace trunk/lib/solr-solrj.jar with the older version and made a
clean build then. Sorry for the sketchy wording. Whireshark does not work with
localhost connections on Windows, so I looked into the code using the debugger.
For all I can see there is a POST connection. I think this is a network problem
and does not depend on manifold.
The unexpected job status encountered exceptions were most propably caused by
the wrong character collation in MySQL. Having no admin rights, I had to create
the schema manually and the default collation is case insensitive. So there was
no difference when querying status values which occur in upper and lower case.
> 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)
