You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2016/05/03 16:31:12 UTC
[jira] [Resolved] (SOLR-8933) SolrDispatchFilter::consumeInput logs
"Stream Closed" IOException
[ https://issues.apache.org/jira/browse/SOLR-8933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller resolved SOLR-8933.
-------------------------------
Resolution: Fixed
Fix Version/s: 6.1
master
> SolrDispatchFilter::consumeInput logs "Stream Closed" IOException
> -----------------------------------------------------------------
>
> Key: SOLR-8933
> URL: https://issues.apache.org/jira/browse/SOLR-8933
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.10.3
> Reporter: Mike Drob
> Assignee: Mark Miller
> Fix For: master, 6.1
>
> Attachments: SOLR-8933.patch, SOLR-8933.patch, SOLR-8933.patch, SOLR-8933.patch, SOLR-8933.patch, SOLR-8933.patch, SOLR-8933.patch, SOLR-8933.patch, SOLR-8933.patch, SOLR-8933.patch, SOLR-8933.patch
>
>
> After SOLR-8453 we started seeing some IOExceptions coming out of SolrDispatchFilter with "Stream Closed" messages.
> It looks like we are indeed closing the request stream in several places when we really need to be letting the web container handle their life cycle. I've got a preliminary patch ready and am working on testing it to make sure there are no regressions.
> A very strange piece of this is that I have been entirely unable to reproduce it on a unit test, but have seen it on cluster deployment quite consistently.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org