You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mikhail Khludnev (JIRA)" <ji...@apache.org> on 2016/10/03 18:27:20 UTC

[jira] [Comment Edited] (SOLR-9182) Test OOMs when ssl + clientAuth

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

Mikhail Khludnev edited comment on SOLR-9182 at 10/3/16 6:26 PM:
-----------------------------------------------------------------

[^SOLR-9182.patch] makes the cursed seed ( https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/17953/) pass locally.

I'm absolutely not sure about the approach taken, and hardly able to come up with a proper testing approach. And, btw, what's a clientAuth after all? Seriously, what a proper key for caching http contexts? 


was (Author: mkhludnev):
[^SOLR-9182.patch] make cursed seed ( https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/17953/) pass locally.

I'm absolutely not sure about the approach taken, and hardly able to come up with a proper testing approach. And, btw, what's a clientAuth after all? Seriously, what a proper key for caching http contexts? 

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