You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've changed for secure Random is configured in 1.47.0 release.
You can now configure the algorithm explicitly via Archive.Context#secureRandomAlgorithm(java.lang.String) or aeron.secure.random.algorithm system property. The default algorithm value is OS specified, i.e. on Windows it is Windows-PRNG otherwise it is NativePRNGNonBlocking.
Hi, sorry to disturb.
We encountered
ConductorServiceTimeoutException
after upgrade aeron to 1.45.0. (We are using Oracle JDK21, our previous aeron version was 1.41.4)It is similar to this issue: #1688 and we reproduce this problem using very simple code:
After diagnostic, we found the root cause via stack info.
As https://stackoverflow.com/questions/70768857/securerandom-is-unreasonably-slow-or-freezes-the-system mentioned, this was caused by
SecureRandom
, the solutions mentioned here, however, do not apply to our scenario.In
ArchiveConductor
, line2596
:This code calls
SecureRandom.getInstanceStrong()
which use property in security config file to create random seed.So we have to set security property manually to deal with it.
We're not sure this is as expected.
Looking forward to any replies.
Other references:
https://tersesystems.com/blog/2015/12/17/the-right-way-to-use-securerandom/
https://www.unix.com/man_page/centos/4/urandom/
The text was updated successfully, but these errors were encountered: