Do you know if this is a known issue with JVM and a bug is filed? If
this is not expected to be fixed anytime soon, we might be able to work
around.
If you can, please try some other varition of SecureRandom that works on
your platform. Otherwise we might replace it with something else. We
used SecureRandom only because we didn't want random number based on
only time as seed. We could change the seed to something else.
Raghu.
闫雪冰 wrote:
> Hi dhruba,
>
> What pointed us to SecureRandom was the stack trace in log file for
> DataNode, after the 'hadoop dfs -put' failed, my colleague York stepped in
> from there and found the problem out.
>
> I've written a little program on my box (running FreeBSD4.11-YAHOO-20070423,
> you might be familiar with , :P) to test the call to
> SecureRandom.getInstance("SHA1PRNG").nextInt, at which the program always
> hung up, and there was no any exception thrown.
>
> Xuebing
>
