[
https://issues.apache.org/jira/browse/CONNECTORS-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13964143#comment-13964143
]
Hiroshi Tatsumi commented on CONNECTORS-920:
--------------------------------------------
Thank you for modifying the code. I read the change r1585924.
This change, I understand that Solr Connector repeatedly send a document until
Solr can read it.
I guessed that SocketTimeoutException occurred when Solr couldn't read the
document due to Solr's bug or Tika's bug caused by a bad document.
If so, this change causes infinite loop. Do I worry too much?
> 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)
