lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] [Commented] (SOLR-9068) Solaris SSL test failures when using NullSecureRandom?
Date Thu, 05 May 2016 17:04:12 GMT


Uwe Schindler commented on SOLR-9068:

Hi Hoss,

unfortunately, your patch did not change anything. I ran it with and without, in both cases
it always failed on first time when beasting or running standalone.
Maybe we should open a bug report at Oracle and for now disable the tests with {{assumeFalse(Constants.SUN_OS)}}.

If you like a can give you an account on the Solaris machine to try yourself (keep in mind,
it has neither GIT nor ANT installed, totally blank - all is provided by Jenkins).

> Solaris SSL test failures when using NullSecureRandom?
> ------------------------------------------------------
>                 Key: SOLR-9068
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>            Reporter: Hoss Man
>             Fix For: 4.9, master
>         Attachments: SOLR-9068.Lucene-Solr-6.x-Solaris_110.log, SOLR-9068.Lucene-Solr-master-Solaris_558.log,
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message