You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2011/09/23 16:34:26 UTC

[jira] [Updated] (JCR-2795) Initializing SeededSecureRandom may be slow

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

Jukka Zitting updated JCR-2795:
-------------------------------

    Fix Version/s: 2.2.0
       Issue Type: Improvement  (was: Bug)

> Initializing SeededSecureRandom may be slow
> -------------------------------------------
>
>                 Key: JCR-2795
>                 URL: https://issues.apache.org/jira/browse/JCR-2795
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Thomas Mueller
>            Assignee: Thomas Mueller
>            Priority: Minor
>             Fix For: 2.2.0
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira