[
https://issues.apache.org/jira/browse/CONNECTORS-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896788#comment-13896788
]
Karl Wright commented on CONNECTORS-880:
----------------------------------------
Hi Florian,
There are no other known problems in 1.6, but I have been working on the job
state transitions. Specifically, the various kinds of ServiceInterruption from
output connectors are now honored. So if you are using an output connector
that is responding to a request with a ServiceInterruption, then unless that
connector is sending the right variety of ServiceInterruption it is conceivable
that it could retry indefinitely, or at least for much longer than you would
like.
Could you be more specific about which output connector you are using?
> 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)
