[
https://issues.apache.org/jira/browse/SOLR-8933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob updated SOLR-8933:
----------------------------
Attachment: SOLR-8933.patch
bq. Ioutils has a wrapper for this!
Which IOUtils? I didn't see this in {{o.a.lucene.util}} or
{{o.a.solr.common.util}}. I'm currently adding a new class
{{CloseShieldServletInputStream}} inspired by the Apache commons-io
{{CloseShieldInputStream}} which was almost good enough to use. There's maybe
some clever way to handle this via generics, reflection, and proxies, but I
think that suffers in terms of maintainability.
bq. Why not just enable it during "test mode"
Done. Originally I thought there was value in fine grained control to enable
the warning, but at this point I'm not convinced that is true.
> 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
> Attachments: 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
