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 2018/04/29 23:29:00 UTC
[jira] [Updated] (SOLR-12290) Improve our servlet stream closing
prevention code for users and devs.
[ https://issues.apache.org/jira/browse/SOLR-12290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller updated SOLR-12290:
-------------------------------
Summary: Improve our servlet stream closing prevention code for users and devs. (was: Remove response output stream closes that have no affect and review our request/response close protection testing and impl.)
> Improve our servlet stream closing prevention code for users and devs.
> ----------------------------------------------------------------------
>
> Key: SOLR-12290
> URL: https://issues.apache.org/jira/browse/SOLR-12290
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Minor
> Attachments: SOLR-12290.patch, SOLR-12290.patch, SOLR-12290.patch, SOLR-12290.patch
>
>
> Original Summary:
> When you fetch a file for replication we close the request output stream after writing the file which ruins the connection for reuse.
> We can't close response output streams, we need to reuse these connections. If we do, clients are hit will connection problems when they try and reuse the connection from their pool.
> New Summary:
> At some point the above was addressed during refactoring. We should remove these neutered closes and review our close shield code.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org