[
https://issues.apache.org/jira/browse/SOLR-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414571#comment-16414571
]
David Smiley commented on SOLR-10338:
-------------------------------------
I think SolrTestCaseJ4's insistence on this is a bit of an over-reach for
external projects that want to use solr-test-framework. It's well intentioned
but creates an annoying hassle that randomly occurs. When it happens, yes the
exception is helpful but then I have to go modify my build to pass the system
property both in a pom.xml (or equivalent to other build tools) and my IDE
config.
I can see that Solr itself wants this, but solr-test-framework not only serves
testing Solr itself but external players.
Curious: do you know what randomized situation causes this to trip? It's not
clear; I have a reproducible seed but I don't know (without lots of digging)
why usually it won't trip. FWIW I run on a Mac with Java 8.
> Configure SecureRandom non blocking for tests.
> ----------------------------------------------
>
> Key: SOLR-10338
> URL: https://issues.apache.org/jira/browse/SOLR-10338
> Project: Solr
> Issue Type: Sub-task
> Reporter: Mihaly Toth
> Assignee: Mark Miller
> Priority: Major
> Fix For: 7.1, master (8.0)
>
> Attachments: SOLR-10338.patch, SOLR-10338.patch, SOLR-10338.patch,
> SOLR-10338.patch, SOLR-10338.patch, SOLR-10338.patch, SOLR-10338.patch,
> SOLR-10338.patch
>
>
> It would be best if SecureRandom could be made non blocking. In that case we
> could get rid of random entropy exhaustion issue related to all usages of
> SecureRandom.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
