[
https://jira.duraspace.org/browse/DS-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26982#comment-26982
]
Ian Boston commented on DS-1396:
--------------------------------
[~helix84] re:http://www.itonguard.com/20090313/weblogic-starts-slow/
Thanks for the pointer. I already had -Djava.security.egd=file:/dev/./urandom
on the command line (tip 1) and putting securerandom.source=file:/dev/./urandom
which does the same thing, makes no difference. It was already
securerandom.source=file:/dev/urandom see JDK bug 6202721 for why you need the
/./, detailed explanation is in JDK bug id 4705093.
http://bugs.sun.com/view_bug.do?bug_id=4705093. Since seeding SecureRandom only
takes 20 bytes (from either source) and I have tested /dev/random with rngtest
at 7Mbits/s it may not be an issue with /dev/random. While I have been writing
this I restarted tomcat. Bringing the DSpaceKernel up has been paused now for
about 10 minutes.
The fact that rngtest reports 7Mbit/s of bits available from /dev/random
indicates this might not be an OS level issue.
If I stop tomcat, remove all the DSpace webapps and put the standard tomcat
ones back in the container takes 703ms to start.
23-Nov-2012 01:55:46 org.apache.catalina.core.AprLifecycleListener init
23-Nov-2012 01:55:46 org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-nio-127.0.0.1-8080"]
23-Nov-2012 01:55:46 org.apache.tomcat.util.net.NioSelectorPool
getSharedSelector
INFO: Using a shared selector for servlet write/read
23-Nov-2012 01:55:46 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 913 ms
23-Nov-2012 01:55:46 org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
23-Nov-2012 01:55:46 org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.33
23-Nov-2012 01:55:46 org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /dspace3/webapps/docs
23-Nov-2012 01:55:47 org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /dspace3/webapps/ROOT
23-Nov-2012 01:55:47 org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /dspace3/webapps/examples
23-Nov-2012 01:55:47 org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-nio-127.0.0.1-8080"]
23-Nov-2012 01:55:47 org.apache.catalina.startup.Catalina start
INFO: Server startup in 703 ms
I think, that indicates the issue is not with Tomcat or Java on this platform.
I'll write a small test webapp to prove or disprove this is an issue with
SecureRandom on this platform
> Very slow startup on Linux Platforms
> ------------------------------------
>
> Key: DS-1396
> URL: https://jira.duraspace.org/browse/DS-1396
> Project: DSpace
> Issue Type: Bug
> Affects Versions: 3.0
> Environment: Linux version 2.6.32-38-server (buildd@allspice) (gcc
> version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) )
> /usr/lib/jvm/java-6-sun/bin/java
> -Djava.util.logging.config.file=/usr/local/tomcat7/conf/logging.properties
> -Djava.awt.headless=true -Djava.security.egd=file:/dev/./urandom -Xms256m
> -Xmx800m -XX:PermSize=256m -XX:NewSize=64m -server -XX:+UseConcMarkSweepGC
> -Djava.net.preferIPv4Stack=true
> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
> -Djava.endorsed.dirs=/usr/local/tomcat7/endorsed -classpath
> /usr/local/tomcat7/bin/bootstrap.jar:/usr/local/tomcat7/bin/tomcat-juli.jar
> -Dcatalina.base=/usr/local/tomcat7 -Dcatalina.home=/usr/local/tomcat7
> -Djava.io.tmpdir=/tmp/tomcat7-tmp org.apache.catalina.startup.Bootstrap start
> Reporter: Ian Boston
> Priority: Critical
>
> I am experiencing extremely slow startup times for DS3-rc3 on Linux with the
> stock sun JVM, and I have experienced total hangs 11:19-15:09 of the JVM with
> perfect operation after the end of the period (no restart of any form was
> required). By slow startup I mean just bringing up solr, xmlui and jspui can
> take 60 minutes.
> I think this is due to /dev/ramdom on the OS not getting sufficient entropy,
> probably caused by the Bouncy Castle crypto APIs or the new SecureRandom() in
> Eperson.
> performing a
> find /
> as root appears to unstick the JVM on startup, pointing to an entropy issue
> (find / will cause disk I/O not from cache generating low level device driver
> entropy)
> Has anyone else seen these issues ?
> Is there a known fix (other than performing a find)
> I have already tried -Djava.security.egd=file:/dev/./urandom
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
