[
https://issues.apache.org/jira/browse/SOLR-9182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542159#comment-15542159
]
Alan Woodward commented on SOLR-9182:
-------------------------------------
According to
http://hc.apache.org/httpcomponents-client-ga/tutorial/html/advanced.html#stateful_conn,
if we're using client auth then we need to re-use HttpClientContexts between
requests, otherwise we don't share pooled connections and have to
re-authenticate every time.
Currently, we generate a new HttpClientContext every time HttpClient.execute()
is called.
I think we can cache HttpClientContexts in the following places:
* HttpSolrCall
* HttpSolrClient
* ConcurrentUpdateSolrClient
> Test OOMs when ssl + clientAuth
> -------------------------------
>
> Key: SOLR-9182
> URL: https://issues.apache.org/jira/browse/SOLR-9182
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
>
> the combination of SOLR-9028 fixing SSLTestConfig to actually pay attention
> to clientAuth setting, and SOLR-9107 increasing the odds of ssl+clientAuth
> being tested has helped surface some more tests that seem to fairly
> consistently trigger OOM when running with SSL+clientAuth.
> I'm not sure if there is some underlying memory leak somewhere in the SSL
> code we're using, or if this is just a factor of increased request/response
> size when using (double) encrypted requests, but for now I'm just focusing on
> opening a tracking issue for them and suppressing SSL in these cases with a
> link here to clarify *why* we're suppressing SSL.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
