Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [5,015] milliseco

最新推荐文章于 2022-04-01 11:25:57 发布
最新推荐文章于 2022-04-01 11:25:57 发布
阅读量115 收藏
点赞数
CC 4.0 BY-SA版权
原文链接：https://my.oschina.net/luleilei516/blog/1799242
本文分析了Tomcat启动过程中耗时较长的问题，并给出了具体的错误信息：“Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [5,015] milliseconds.” 提供了两个链接作为解决方案的参考。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

Problem: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took...
d3y1`5 81_09
11-15 1299
Problem WARNING [main] org.apache.catalina.util.SessionIdGeneratorBase.createSecureRandom Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [1,139,942] milliseconds. So...
Tomcat启动时Creation of SecureRandom instance for session ID很慢
weixin_30343157的博客
11-20 210
启动tomcat很慢，检查后发现：[localhost-startStop-1] org.apache.catalina.util.SessionIdGeneratorBase.createSecureRandom Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [131,830] ...
Tomcat 启动时 SecureRandom 非常慢解决办法
weixin_34258838的博客
10-13 498
Tomcat 启动时 SecureRandom 非常慢解决办法作者：张松然 字体：[增加减小] 类型：转载 时间：2017-06-25我要评论这篇文章主要介绍了Tomcat 启动时 SecureRandom 非常慢解决办法的相关资料,需要的朋友可以参考下Tomcat 启动时 SecureRandom 非常慢解决办法最近使用阿里云的 Ubuntu 16.04 ESC 服务器...
Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [33,755] milliseco
{丸の子}
06-28 1679
刚部署好程序，第一次登录时，加载非常得慢，查看log日志发现：Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [33,755] milliseconds. 说什么创建用于会话ID生成的SecureRandom实例花费了[33,755]毫秒。 解决办法：打开$JAVA_PATH/jre/lib/security/java.security这个文件，找到下面的内容： securerandom.
Tomcat启动Creation of SecureRandom instance 卡住解决办法
weixin_44387972的博客
10-23 1273
本文描述Tomcat启动因为 Creation of SecureRandom instance for session ID generation using [SHA1PRNG] 卡住的问题，以及At least one JAR was scanned for TLDs yet contained no TLDs 解决办法 最初是升级dubbo项目开始，项目启动变慢一两分钟，后边突然就很过分十分钟，甚至还要多。 导致几乎不能再白天随意发版了，找到两个问题奇怪的日志 1. At least one
Spring boot ：Creation of SecureRandom instance for session ID generation using
悟能的师兄的专栏
12-01 4918
最近在写一个分享数据网站，使用spring boot，打成war包发布。很方便 可是在新买的阿里云上面老出现，启动五六分钟后，整个服务才zhen真正启动成功。烦的我呀，马上查一把 就是这个在捣鬼，查到了优快云的另一外大神的解决方法，完美解决问题，因为那位大神用的JDK1.7。处理的是tomcat， 我这边处理的是Spring boot :java -jar feitian.war的方式，所...
警告: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [458] milliseconds.
06-09
这个警告是指在生成会话 ID 时，使用了 SHA1PRNG 算法生成 SecureRandom 实例，并且生成实例的过程花费了 458 毫秒的时间。SecureRandom 是用于生成随机数的类，而会话 ID 是用于在客户端和服务器之间识别会话的唯一...
springsecurity使用logout报错Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [614] milliseconds.
05-15
Spring Security 在生成会话 ID 时使用了 SecureRandom 实例，并且默认使用 SHA1PRNG 算法。由于这个算法需要生成随机数，在某些情况下可能需要较长时间来生成，因此会导致超时。 要解决这个问题，你可以尝试以下几...
025-07-10 10:05:43.040 [http-nio-8000-exec-3] WARN org.apache.catalina.util.SessionIdGeneratorBase - Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [116] milliseconds. 2025-07-10 10:05:43.141 [http-nio-8000-exec-3] ERR
最新发布
07-11
首先，用户的问题是关于Java Web应用中出现的警告信息："WARN org.apache.catalina.util.SessionIdGeneratorBase - Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [116] ...
信息: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib 6月 07, 2025 4:55:21 下午 org.apache.coyote.AbstractProtocol init 信息: Initializing ProtocolHandler ["http-nio-0.0.0.0-8080"] 6月 07, 2025 4:55:21 下午 org.apache.tomcat.util.net.NioSelectorPool getSharedSelector 信息: Using a shared selector for servlet write/read 6月 07, 2025 4:55:21 下午 org.apache.coyote.AbstractProtocol init 信息: Initializing ProtocolHandler ["ajp-nio-8009"] 6月 07, 2025 4:55:21 下午 org.apache.coyote.AbstractProtocol init 严重: Failed to initialize end point associated with ProtocolHandler ["ajp-nio-8009"] java.lang.IllegalArgumentException: timeout < 0 at java.base/sun.nio.ch.ServerSocketAdaptor.setSoTimeout(ServerSocketAdaptor.java:162) at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:352) at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:823) at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:476) at org.apache.catalina.connector.Connector.initInternal(Connector.java:960) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) at org.apache.catalina.core.StandardService.initInternal(StandardService.java:568) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:871) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) at org.apache.catalina.startup.Catalina.load(Catalina.java:592) at org.apache.catalina.startup.Catalina.load(Catalina.java:615) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:308) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:482) 6月 07, 2025 4:55:21 下午 org.apache.catalina.core.StandardService initInternal 严重: Failed to initialize connector [Connector[AJP/1.3-8009]] org.apache.catalina.LifecycleException: Failed to initialize component [Connector[AJP/1.3-8009]] at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107) at org.apache.catalina.core.StandardService.initInternal(StandardService.java:568) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:871) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) at org.apache.catalina.startup.Catalina.load(Catalina.java:592) at org.apache.catalina.startup.Catalina.load(Catalina.java:615) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:308) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:482) Caused by: org.apache.catalina.LifecycleException: Protocol handler initialization failed at org.apache.catalina.connector.Connector.initInternal(Connector.java:962) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) ... 12 more Caused by: java.lang.IllegalArgumentException: timeout < 0 at java.base/sun.nio.ch.ServerSocketAdaptor.setSoTimeout(ServerSocketAdaptor.java:162) at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:352) at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:823) at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:476) at org.apache.catalina.connector.Connector.initInternal(Connector.java:960) ... 13 more 6月 07, 2025 4:55:21 下午 org.apache.catalina.startup.Catalina load 信息: Initialization processed in 8287 ms 6月 07, 2025 4:55:22 下午 org.apache.catalina.core.StandardService startInternal 信息: Starting service Catalina 6月 07, 2025 4:55:22 下午 org.apache.catalina.core.StandardEngine startInternal 信息: Starting Servlet Engine: Apache Tomcat/8.0.53 6月 07, 2025 4:55:29 下午 org.apache.jasper.servlet.TldScanner scanJars 信息: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time. 6月 07, 2025 4:55:30 下午 org.apache.catalina.util.SessionIdGeneratorBase createSecureRandom 警告: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [319] milliseconds. 6月 07, 2025 4:55:34 下午 org.apache.jasper.servlet.TldScanner scanJars 信息: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time. 6月 07, 2025 4:55:34 下午 org.apache.coyote.AbstractProtocol start 信息: Starting ProtocolHandler ["http-nio-0.0.0.0-8080"] 6月 07, 2025 4:55:35 下午 org.apache.catalina.startup.Catalina start
06-08
我们面对三个主要问题：1.APR库未找到（不影响启动，但影响性能）2.AJP连接器初始化失败（timeout）3.MySQL驱动类加载失败（ClassNotFoundException）下面逐一解决：###1.解决APR库未找到问题APR...
搭建JavaWeb服务器步骤详解
08-28
INFO: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [5172] milliseconds. 关于这个问题，Tomcat 7+版本中使用SecureRandom类来生成随机数，用于会话ID生成和其他地方。...
Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [184,726] millisec
mjlfto的博客
07-03 9523
正常的启动tomcat8而且并没有报错，等待了很久终于看到日志打印出来启动成功了请看下面 Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [184,726] milliseconds. Tomcat 7/8都使用org.apache.catalina.util.Sessi
tomcat启动慢， Creation of SecureRandom instance for session ID generation using [SHA1PRNG]took [xx] mil
落叶翩翩的优快云博客
10-25 1524
通常情况下，tomcat启动只要7-8秒钟，突然有一天，tomcat启动非常慢，要花5~6分钟，甚至更久，以下是解决方案 SHA1PRNG算法是基于SHA-1算法实现且保密性较强的伪随机数生成器。 在SHA1PRNG中，有一个种子产生器，它根据配置执行各种操作。 1）如果Java.security.egd属性或securerandom.source属性指定的是”fil
【解决】Linux Tomcat启动慢--Creation of SecureRandom instance for session ID generation using [SHA1PRNG] to
Yang_yangyang的博客
04-01 782
一、背景 今天部署项目到tomcat，执行./startup.sh命令之后，访问项目迟迟加载不出来，查看日志又没报错（其实是我粗心了，当时tomcat日志还没打印完），一开始怀疑是阿里云主机出现问题，访问ip:80发现nginx运行正常。在我百思不得其解时，项目访问正常了，查看启动日志，发现如下： 15-Mar-2018 16:41:02.302 WARNING [main] org.apache.catalina.util.SessionIdGeneratorBase.createSecureRandom
Linux Tomcat启动慢--Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [
weixin_44773374的博客
11-09 263
https://www.cnblogs.com/yeyu1314/p/10145161.html
解决 Creation of SecureRandom instance for session ID generation using [SHA1PRNG]took [xx] mil
爱吃大西瓜的博客
05-18 4453
找到文件$JAVA_PATH/jre/lib/security/java.security 将securerandom.source的值改为: securerandom.source=file:/dev/./urandom
Tomcat启动缓慢 Creation of SecureRandom instance for ... 花费时间过长的解决方法
Demon
12-17 3904
发现Tomcat启动非常缓慢，5分钟的样子才启动完毕。查看日志，发现Creation of SecureRandom instance for session ID generation这一步骤花费时间过多。 Dec 17, 2016 5:12:04 PM org.apache.catalina.util.SessionIdGeneratorBase createSecureRandom INF
Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [33,755] milliseco...
dining6826的专栏
04-25 820
刚部署好程序，第一次登录时，加载非常得慢，查看log日志发现：Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [33,755] milliseconds. 说什么创建用于会话ID生成的SecureRandom实例花费了[33,755]毫秒。解决办法：打开$JAVA_PAT...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值