[
https://issues.apache.org/jira/browse/SOLR-9604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15549940#comment-15549940
]
Mikhail Khludnev edited comment on SOLR-9604 at 10/5/16 9:04 PM:
-----------------------------------------------------------------
attaching [^SOLR-9604-6x.patch]
HttpSolrClient*ConPoolTest works (and fails) as expected.
ConnectionReuseTest asserts makes me wonder (I swapped two lines to fix one
failure for null metrics). It fails so far SOLR-9608.
was (Author: mkhludnev):
attaching [^SOLR-9604-6x.patch]
HttpSolrClient*ConPoolTest works (and fails) as expected.
ConnectionReuseTest asserts makes me wonder. It fails so far.
> Pooled SSL connections are not being reused with client authentication
> ----------------------------------------------------------------------
>
> Key: SOLR-9604
> URL: https://issues.apache.org/jira/browse/SOLR-9604
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Attachments: SOLR-9604-6x.patch, SOLR-9604.patch, SOLR-9604.patch,
> fails with null.png
>
>
> Solr isn't setting user tokens on any of its HttpClientContext objects when
> requested new http connections. This means that when SSL + client
> authentication is used, HttpClient is creating a new connection on every
> request, to ensure that authentication tokens aren't shared between different
> users. We end up with lots of unused open connections in the connection
> pool, leading to slowness and out-of-memory errors.
--
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
