Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [184,726] millisec
2017-07-03 16:38
831 查看
正常的启动tomcat8而且并没有报错,等待了很久终于看到日志打印出来启动成功了
请看下面
Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [184,726] milliseconds.
Tomcat 7/8都使用org.apache.catalina.util.SessionIdGeneratorBase.createSecureRandom类产生安全随机类SecureRandom的实例作为会话ID,这里花去了455秒。就是这里花了大量的时间去。
有两种解决办法:
1.在Tomcat环境中解决
可以通过配置JRE使用非阻塞的Entropy Source。
在catalina.sh中加入这么一行:-Djava.security.egd=file:/dev/./urandom 即可。
加入后再启动Tomcat,整个启动耗时下降到Server startup in 6213 ms,大大降低了启动的时间。
2.在JVM环境中解决
先执行which javac命令检查jdk安装路径
/usr/local/java/jdk1.8.0_92/bin/javac
去到$JAVA_PATH/jre/lib/security/java.security这个文件,找到下面的内容:
securerandom.source=file:/dev/urandom
替换成
securerandom.source=file:/dev/./urandom
这样问题就解决了
本文出处:原文出处
请看下面
Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [184,726] milliseconds.
Tomcat 7/8都使用org.apache.catalina.util.SessionIdGeneratorBase.createSecureRandom类产生安全随机类SecureRandom的实例作为会话ID,这里花去了455秒。就是这里花了大量的时间去。
有两种解决办法:
1.在Tomcat环境中解决
可以通过配置JRE使用非阻塞的Entropy Source。
在catalina.sh中加入这么一行:-Djava.security.egd=file:/dev/./urandom 即可。
加入后再启动Tomcat,整个启动耗时下降到Server startup in 6213 ms,大大降低了启动的时间。
2.在JVM环境中解决
先执行which javac命令检查jdk安装路径
/usr/local/java/jdk1.8.0_92/bin/javac
去到$JAVA_PATH/jre/lib/security/java.security这个文件,找到下面的内容:
securerandom.source=file:/dev/urandom
替换成
securerandom.source=file:/dev/./urandom
这样问题就解决了
本文出处:原文出处
相关文章推荐
- tomcat启动慢, Creation of SecureRandom instance for session ID generation using [SHA1PRNG]took [xx] mil
- 【解决】Linux Tomcat启动慢--Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [236,325] milliseconds
- Creation of SecureRandom instance for session ID generation using [SHA1PRNG]took [xx] milliseconds
- Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [32,176] milliseco
- WARNING [main] org.apache.catalina.util.SessionIdGeneratorBase.createSecureRandom Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [] milliseconds.
- tomcat 启动慢 Creation of SecureRandom instance for session ID generation using [SHA1PRNG]took [xx] mil
- [置顶] tomcat启动慢, Creation of SecureRandom instance for session ID generation using [SHA1PRNG]took [xx] mil
- tomcat启动慢, Creation of SecureRandom instance for session ID generation using [SHA1PRNG]took [xx] mil
- tomcat 启动慢 Creation of SecureRandom instance for session ID generation using [SHA1PRNG]
- Tomcat7在Centos环境下启动缓慢,SecureRandom instance for session ID generation using[SHA1PRNG] took [530,729]
- springBoot 验证码加载特别慢 Creation of SecureRandom instance for session ID generation
- Tomcat启动 Creation of SecureRandom instance for session ID
- Tomcat启动时Creation of SecureRandom instance for session ID很慢
- tomcat启动太慢,耗时很长的问题 Creation of SecureRandom instance for ...
- Tomcat启动缓慢 Creation of SecureRandom instance for ... 花费时间过长的解决方法
- Using Class of Secure Transport (COST) to Restrict Instance Registration in Oracle RAC (Doc ID 13408
- oratop - Utility for Near Real-time Monitoring of Databases, RAC and Single Instance (Doc ID 1500864
- 论文阅读-A Workflow for Visual Diagnostics of Binary Classifiers using Instance-Level Explanations
- How to Enable SQL_TRACE for Another Session or in MTS Using Oradebug(文档 ID 1058210.6)
- Are you looking for a way to get the entire text of a word document into a RichEdit without using the Clipboard?