[
https://issues.apache.org/jira/browse/CONNECTORS-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560589#comment-13560589
]
Karl Wright commented on CONNECTORS-616:
----------------------------------------
The change you made forces a new HttpClient instance, connection pool, and
HttpSolrServer instance for every document indexed, without even cleaning up
the old pool or instance. So if the problem is happening because the Solr
server is closing a socket that has been reused, then you have guaranteed no
problem with this change - except that you will leak sockets all over the place.
So I don't think we can use this, but it does help us figure out what is going
on.
> Solr Connector gets broken pipe IOExceptions a lot
> --------------------------------------------------
>
> Key: CONNECTORS-616
> URL: https://issues.apache.org/jira/browse/CONNECTORS-616
> Project: ManifoldCF
> Issue Type: Bug
> Components: Lucene/SOLR connector
> Affects Versions: ManifoldCF 1.1
> Reporter: Karl Wright
> Assignee: Karl Wright
> Priority: Blocker
> Fix For: ManifoldCF 1.1
>
>
> Simple history is showing the following:
> {code}
> 01-18-2013 11:27:37.444 document ingest (1)
> file://///192.168.11.5/Sales/1-Quote/Quote-AAA.xls
> FAILED 16896 3 IOException occured when talking to server at:
> http://localhost:8983/solr: Broken pipe
> 01-18-2013 11:27:37.256 document ingest (1)
> file://///192.168.11.5/Sales/1-Quote/Quote-BBB.xls
> FAILED 16896 2 IOException occured when talking to server at:
> http://localhost:8983/solr: Broken pipe
> {code}
> Broken pipe exceptions should be being considered a Solr document rejection,
> akin to a 4xx error code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
