jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-2795) Initializing SeededSecureRandom may be slow
Date Wed, 20 Oct 2010 11:27:25 GMT

     [ https://issues.apache.org/jira/browse/JCR-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas Mueller resolved JCR-2795.
---------------------------------

    Resolution: Fixed

> Initializing SeededSecureRandom may be slow
> -------------------------------------------
>
>                 Key: JCR-2795
>                 URL: https://issues.apache.org/jira/browse/JCR-2795
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>            Priority: Minor
>
> For systems where reading from /dev/random is very slow (so that the alternative seed
algorithm is used), initializing the org.apache.jackrabbit.core.id.SeededSecureRandom singleton
may be very slow, because it is not synchronized. Each thread that calls SeededSecureRandom.getInstance()
will wait up to 1 second until the singleton is initialized.
> At the same time, I would like to add more entropy to the alternative seed algorithm.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message