[
https://issues.apache.org/jira/browse/SOLR-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982128#comment-15982128
]
Hoss Man commented on SOLR-10338:
---------------------------------
bq. ... try to set java.security.egd if it is unset. ...
off the top of my head, I suspect that won't work at all because IIRC the
java.security.\* sysprops are all read on JVM startup as part of initializing
the SecurityManager. So it most likely won't have any effect other then to
confuse any subsequent Solr test-framework specific code that may try to read
that sysprop to sanity check things.
(And even if it does work today, I don't know that the JVM spec guarantees it
will work with future versions of the JVM tomorrow.)
If any part of the spec *does* guarantee that it can/will work, then we should
should use *only* that approach to set "java.security.egd" on test startup (via
a {{static}} block somewhere) and skip all the changes to our build.xml,
eclipse/IDEA configs, etc...
> 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
> Fix For: 6.6, master (7.0)
>
> Attachments: 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
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
