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

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

I'm using a Solr output connection. Manually sending a document to its update 
handler does not raise any problems, however, Manifold seems to receive only 
service interruptions. No document gets indexed.

 WARN 2014-02-11 10:17:36,592 (Job notification thread) - IO exception during 
commit: The target server failed to respond
org.apache.http.NoHttpResponseException: The target server failed to respond
        at 
org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:95)
        at 
org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:61)
        at 
org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:254)
        at 
org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:289)
        at 
org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:252)
        at 
org.apache.http.impl.conn.ManagedClientConnectionImpl.receiveResponseHeader(ManagedClientConnectionImpl.java:191)
        at 
org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:300)
        at 
org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:127)
        at 
org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:715)
        at 
org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:520)
        at 
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906)
        at 
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:805)
        at 
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:784)
        at 
org.apache.manifoldcf.agents.output.solr.ModifiedHttpSolrServer.request(ModifiedHttpSolrServer.java:291)
        at 
org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:197)
        at 
org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(AbstractUpdateRequest.java:117)
        at 
org.apache.manifoldcf.agents.output.solr.HttpPoster$CommitThread.run(HttpPoster.java:1219)
 WARN 2014-02-11 10:17:36,592 (Job notification thread) - Service interruption 
notifying connection - retrying: IO exception during commit: The target server 
failed to respond
org.apache.manifoldcf.agents.interfaces.ServiceInterruption: IO exception 
during commit: The target server failed to respond
        at 
org.apache.manifoldcf.agents.output.solr.HttpPoster.handleIOException(HttpPoster.java:477)
        at 
org.apache.manifoldcf.agents.output.solr.HttpPoster.handleSolrServerException(HttpPoster.java:357)
        at 
org.apache.manifoldcf.agents.output.solr.HttpPoster.commitPost(HttpPoster.java:304)
        at 
org.apache.manifoldcf.agents.output.solr.SolrConnector.noteJobComplete(SolrConnector.java:744)
        at 
org.apache.manifoldcf.crawler.system.JobNotificationThread.run(JobNotificationThread.java:121)

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

Reply via email to