[
https://issues.apache.org/jira/browse/CONNECTORS-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13964186#comment-13964186
]
Karl Wright edited comment on CONNECTORS-920 at 4/9/14 2:28 PM:
----------------------------------------------------------------
Hi Hitoshi,
When Solr cannot process a document, it does not throw a
SocketTimeoutException. It returns either a 400, or a 500 (when there's a Tika
exception, etc.) So I think that this is already handled.
Also, ManifoldCF 1.6 does not retry indefinitely with service interruptions.
The ServiceInterruption exception itself indicates the number (or duration) of
the retries. So there are no infinite loops here.
was (Author: [email protected]):
Hi Hitoshi,
When Solr cannot process a document, it does not throw a
SocketTimeoutException. It returns either a 400, or a 500 (when there's a Tika
exception, etc.) So I think that this is already handled.
> Solr Connector doesn't handle embedded SocketTimeoutException properly
> ----------------------------------------------------------------------
>
> Key: CONNECTORS-920
> URL: https://issues.apache.org/jira/browse/CONNECTORS-920
> Project: ManifoldCF
> Issue Type: Bug
> Components: Lucene/SOLR connector
> Affects Versions: ManifoldCF 1.5.1
> Reporter: Karl Wright
> Assignee: Karl Wright
> Fix For: ManifoldCF 1.6
>
>
> As reported in the user list:
> "I'm using MCF1.5.1 and Solr4.6.1.
> When I use SolrConnecotor, sometimes SolrServerException occurs.
> Normally, SolrServerException is caught by HttpPoster, line 950.
> But in my case, the inner exception of SolrServerException is
> SocketTimeoutException, not SocketException.
> So, activityCode is set to failed, then mcf interrupt the crawl process.
> In this case, I expect that mcf shouldn't interrupt the crawl process.
> Mcf should skip the invalid file.
> Could you modify the mcf code, or provide a option?
> If you could, I'm glad to being modified in the future version."
--
This message was sent by Atlassian JIRA
(v6.2#6252)
