我有一个在AWS上运行的weblogic服务器。我对其进行了AMI备份,并从AMI创建了新实例。
在新实例中,当我尝试启动weblogic时,它停留在以下状态。
<Dec 11, 2018 12:00:01 AM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 >
<Dec 11, 2018 12:00:02 AM IST> <Notice> <WebLogicServer> <BEA-000365>
<Server state changed to STARTING>
<Dec 11, 2018 12:00:02 AM IST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Dec 11, 2018 12:00:02 AM IST> <Notice> <Log Management> <BEA-170019> <The server log file /home/weblogic/Oracle/Middleware/user_projects/domains/ClassicDomain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.
另请参见https://pastebin.com/D9MYSvBj上JVM的线程转储
任何帮助将不胜感激。
-阿伦
答案 0 :(得分:0)
问题已解决。
在线程转储中,我发现了
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=10 tid=0x00007fda6aad4800 nid=0x6a3b runnable [0x00007fda41d5d000]
java.lang.Thread.State: RUNNABLE
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:220)
at sun.security.provider.SeedGenerator$URLSeedGenerator.getSeedBytes(SeedGenerator.java:493)
at sun.security.provider.SeedGenerator.generateSeed(SeedGenerator.java:117)
at sun.security.provider.SecureRandom$SeederHolder.<clinit>(SecureRandom.java:167)
at sun.security.provider.SecureRandom.engineNextBytes(SecureRandom.java:184)
- locked <0x00000000ece53ac0> (a sun.security.provider.SecureRandom)
at java.security.SecureRandom.nextBytes(SecureRandom.java:433)
- locked <0x00000000ece53d60> (a java.security.SecureRandom)
at oracle.ldap.util.guid.GUIDParamGenerator.generateClockSequence(GUIDParamGenerator.java:128)
在Google中进行了一些搜索,并找到了更改$ JAVA_HOME / jre / lib / security / java.security中以下行的解决方案
来自
securerandom.source=file:/dev/urandom
收件人
securerandom.source=file:/dev/./urandom
然后重新启动weblogic解决了该问题。
Ref:http://ruleoftech.com/2016/avoiding-jvm-delays-caused-by-random-number-generation
谢谢 阿伦