[
https://issues.apache.org/jira/browse/CONNECTORS-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560648#comment-13560648
]
Karl Wright commented on CONNECTORS-616:
----------------------------------------
Hi Abe-san, the HttpComponents group recommends that we get a WireShark or
tcpdump capture. That way we can see who is closing the connection for
certain. Unfortunately since this using localhost that won't work. But if you
have more than one machine at your office maybe this will be possible for you?
It's a challenge for me because I don't have the hardware at home.
> 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
