manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Florian Schmedding (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONNECTORS-880) Under the right conditions, job aborts do not update "last checked" time
Date Tue, 11 Feb 2014 22:29:20 GMT

    [ https://issues.apache.org/jira/browse/CONNECTORS-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898413#comment-13898413
] 

Florian Schmedding commented on CONNECTORS-880:
-----------------------------------------------

I just replaced httpclient library (without re-building) and now the HTTP POST works fine.
I noticed that all connections except those from Manifold appeared with the address 0:0:0:0:0:0:0:1
instead of 127.0.0.1. There is a resolved issue about IPv6 addresses: https://issues.apache.org/jira/browse/HTTPCLIENT-1317.
I don't know if this was really the cause of this trouble, but anyway, the new version works.

mcf-combined-service.war: 
httpclient.jar -> httpclient-4.3.2.jar
httpcore.jar -> httpcore-4.3.1.jar

connector-lib:
httpmime.jar -> httpmime-4.3.2.jar (perhaps not important)

(binary from http://ftp.fau.de/apache//httpcomponents/httpclient/binary/httpcomponents-client-4.3.2-bin.zip
at http://hc.apache.org/downloads.cgi)

After restarting Tomcat all documents get indexed by Solr. Now I configured a schedule to
check the fix you provided. Thanks for your help!



> 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)

Mime
View raw message