You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Alan Woodward (JIRA)" <ji...@apache.org> on 2016/10/05 09:12:20 UTC

[jira] [Commented] (SOLR-9604) Pooled SSL connections are not being reused with client authentication

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

Alan Woodward commented on SOLR-9604:
-------------------------------------

The concurrent client in DistributedUpdateProcessor actually already uses the HttpClient object from UpdateHandler, so I think this is ready to go.

> 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 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org