[
https://issues.apache.org/jira/browse/SOLR-9182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542892#comment-15542892
]
Hoss Man commented on SOLR-9182:
--------------------------------
[~romseygeek]: as noted in some of the comments/commits:
* any tests that were exhibiting OOMs with ssl+clientAuth had {{\@SuppressSSL}}
annotations added to them
* to reproduce you'll almost certianly need to remove those anotations before
attempting to test any fix
* You can also replace {{\@SuppressSSL}} with {{\@RandomizeSSL(1.0)}} to
_force_ these tests to use both ssl and clientAuth (1.0 = 100% odds of using
ssl and 100% odds of using clientAuth)
> 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
> Attachments: SOLR-9182.patch
>
>
> 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]
