You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2016/05/04 18:16:12 UTC

[jira] [Created] (SOLR-9068) Solaris SSL test failures when using NullSecureRandom?

Hoss Man created SOLR-9068:
------------------------------

             Summary: Solaris SSL test failures when using NullSecureRandom?
                 Key: SOLR-9068
                 URL: https://issues.apache.org/jira/browse/SOLR-9068
             Project: Solr
          Issue Type: Sub-task
            Reporter: Hoss Man


In parent issue SOLR-5776, NullSecureRandom was introduced and SSLTestConfig was refactored so that both client & server would use it to prevent blocked threads waiting for entropy.

Since those commits to master & branch_6x, both Solaris jenkins builds have seen failures at the same spots in TestMiniSolrCloudClusterSSL.testSslAndNoClientAuth - and looking at the logs the root cause appears to be intranode communication failures due to "javax.crypto.BadPaddingException"

Perhaps the Solaris SSL impl has bugs in it's padding code that are tickeled when the SecureRandom instance returns long strings of null bytes?



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