[ 
https://issues.apache.org/jira/browse/SOLR-8933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229100#comment-15229100
 ] 

Mark Miller commented on SOLR-8933:
-----------------------------------

bq. I've only seen it on 4.10.3 and Tomcat. As Uwe Schindler alludes to later, 
Jetty might be taking care of this for us.

Okay. Just want anyone reading this issue to be able to understand whether and 
how it might impact them. I still had not seen this have any effect with Jetty 
here.

bq. I wrapped the request and intercepted requests to close() and logged them 
with stack traces. I had removed this for the patch because I wasn't confident 
in the performance impact that I would be causing, but can easily add it back.

I don't think we need it committed, just how you went about it documented. 
Since we can't forbid this from coming into the code again, we at  least want 
to make this easy on the next person who has to tackle it by getting this info 
in the ticket.

Trunk and 6x will always diverge some too, so probably also good to note 
specifically which branch(s) has been cleared.

> 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]

Reply via email to