[
https://issues.apache.org/jira/browse/SOLR-8933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228355#comment-15228355
]
Mark Miller commented on SOLR-8933:
-----------------------------------
Can we clear up the report a bit? I'm kind of confused as it is.
bq. SolrDispatchFilter::consumeInput logs "Stream Closed" IOException
Have we ever actually seen that happen with Jetty or on trunk, or have we still
only seen it with a version of 4.10.3 and Tomcat?
bq. 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.
Same question - a unit test on 4.10.3 version or trunk or both? Same with the
the cluster deployment? Is that older? Tomcat or Jetty?
Just trying to understand when we are talking about our 4.10.3 version, latest
trunk, and Tomcat vs Jetty.
Last I had seen, while we don't want to close these streams early regardless,
on trunk with Jetty, it doesn't actually log anything or cause us any grief.
> SolrDispatchFilter::consumeInput logs "Stream Closed" IOException
> -----------------------------------------------------------------
>
> Key: SOLR-8933
> URL: https://issues.apache.org/jira/browse/SOLR-8933
> Project: Solr
> Issue Type: Bug
> Reporter: Mike Drob
> Assignee: Mark Miller
> Attachments: 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: [email protected]
For additional commands, e-mail: [email protected]
