[
https://issues.apache.org/jira/browse/SOLR-9604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15548675#comment-15548675
]
Mikhail Khludnev edited comment on SOLR-9604 at 10/5/16 1:40 PM:
-----------------------------------------------------------------
bq. Mikhail Khludnev, can you ensure that the test fails if you change
HttpSolrClient so that it passes 'null' instead of 'this' to the context
builder?
absolutely
!fails with null.png!
was (Author: mkhludnev):
bq. Mikhail Khludnev, can you ensure that the test fails if you change
HttpSolrClient so that it passes 'null' instead of 'this' to the context
builder?
absolutely
!fails with null.png|thumbnail!
> 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.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: [email protected]
For additional commands, e-mail: [email protected]
