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

ASF subversion and git services commented on SOLR-9182:
-------------------------------------------------------

Commit 7f821393690624e4d8db4bee45c0645785a72d73 in lucene-solr's branch 
refs/heads/branch_6x from Chris Hostetter
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=7f82139 ]

SOLR-9182: SuppressSSL on some tests where it's non to cause OOM

(cherry picked from commit 1eb6c9f816fa09acf2d55370876f79218c0328c3)

Conflicts:
        
solr/core/src/test/org/apache/solr/cloud/TestTolerantUpdateProcessorRandomCloud.java


> 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]

Reply via email to