[
https://issues.apache.org/jira/browse/SOLR-9068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275155#comment-15275155
]
Uwe Schindler commented on SOLR-9068:
-------------------------------------
Thanks Hoss for fixing!
The remaining question is still: why did it sometimes not like the bytes we
return? Theoretically, our random could also return all 0-bytes - would it fail
then?
As a queick fix this looks good, but I would like to understand it! :-)
> BadPaddingException when running SSL test using NullSecureRandom
> ----------------------------------------------------------------
>
> Key: SOLR-9068
> URL: https://issues.apache.org/jira/browse/SOLR-9068
> 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, SOLR-9068.patch, SOLR-9068.patch
>
>
> 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, all Solaris jenkins builds got
> 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"
> Initial speculation was that perhaps the Solaris SSL impl has bugs in it's
> padding code that are tickled when the SecureRandom instance returns long
> strings of null bytes, but subsequently we got reports of similar, less
> frequently occuring, bugs on other OSs (see SOLR-9082).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
