welogic的受管理服务器无法启动

Posted 百思不得其姐

tags:

篇首语:本文由小常识网(cha138.com)小编为大家整理,主要介绍了welogic的受管理服务器无法启动相关的知识,希望对你有一定的参考价值。

welogic在启动受管理服务器无法启动,如下提示:

***************************************************
*  To start WebLogic Server, use a username and   *
*  password assigned to an admin-level user.  For *
*  server administration, use the WebLogic Server *
*  console at http://hostname:port/console        *
***************************************************
starting weblogic with Java version:
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode)
Starting WLS with line:
/usr/java/jdk1.6.0_45/bin/java -server   -Xms256m -Xmx512m  -XX:MaxPermSize=256m -Dweblogic.Name=server1 -Djava.security.policy=/bea/weblogic/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy  -Dweblogic.ProductionModeEnabled=true -Dweblogic.security.SSL.trustedCAKeyStore=/bea/weblogic/Oracle/Middleware/wlserver_10.3/server/lib/cacerts   -da -Dplatform.home=/bea/weblogic/Oracle/Middleware/wlserver_10.3 -Dwls.home=/bea/weblogic/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/bea/weblogic/Oracle/Middleware/wlserver_10.3/server   -Dweblogic.management.discover=false -Dweblogic.management.server=http://192.168.86.100:7001  -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/bea/weblogic/Oracle/Middleware/patch_wls1036/profiles/default/sysext_manifest_classpath:/bea/weblogic/Oracle/Middleware/patch_ocp371/profiles/default/sysext_manifest_classpath  weblogic.Server
<Oct 23, 2018 10:54:34 PM CST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true> 
<Oct 23, 2018 10:54:34 PM CST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true> 
<Oct 23, 2018 10:54:35 PM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.45-b01 from Sun Microsystems Inc.> 
<Oct 23, 2018 10:54:36 PM CST> <Info> <Security> <BEA-090065> <Getting boot identity from user.> 
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:
<Oct 23, 2018 10:54:45 PM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050 > 
<Oct 23, 2018 10:54:47 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING> 
<Oct 23, 2018 10:54:47 PM CST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool> 
<Oct 23, 2018 10:54:47 PM CST> <Notice> <Log Management> <BEA-170019> <The server log file /bea/weblogic/Oracle/Middleware/user_projects/domains/server_domain/servers/server1/logs/server1.log is opened. All server side log events will be written to this file.> 
<Oct 23, 2018 10:54:50 PM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.> 
<Oct 23, 2018 10:54:53 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY> 
<Oct 23, 2018 10:54:53 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING> 
<Oct 23, 2018 10:54:55 PM CST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.> 
<Oct 23, 2018 10:54:55 PM CST> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster Cluster on 239.192.0.0:7007.> 
<Oct 23, 2018 10:54:55 PM CST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of Cluster.> 
<Oct 23, 2018 10:54:55 PM CST> <Error> <Cluster> <BEA-000110> <Multicast socket receive error: java.net.SocketException: Socket closed
java.net.SocketException: Socket closed
    at java.net.PlainDatagramSocketImpl.receive0(Native Method)
    at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:145)
    at java.net.DatagramSocket.receive(DatagramSocket.java:725)
    at weblogic.cluster.MulticastFragmentSocket.receive(MulticastFragmentSocket.java:239)
    at weblogic.cluster.FragmentSocketWrapper.receive(FragmentSocketWrapper.java:98)
    Truncated. see log file for complete stacktrace
> 
解决:在管理服务器,如server1,server2中找到bin/setDomainEnv.sh,在JAVA_OPTION节加入:-Djava.net.preferIPv4Stack=true。
if [ "${debugFlag}" = "true" ] ; then
        JAVA_DEBUG="-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=${DEBUG_PORT},server=y,suspend=n -Djava.compiler=NONE"
        export JAVA_DEBUG
        JAVA_OPTIONS="${JAVA_OPTIONS} ${enableHotswapFlag} -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole...-Djava.net.preferIPv4Stack=true"
        export JAVA_OPTIONS
else        JAVA_OPTIONS="${JAVA_OPTIONS} ${enableHotswapFlag} -da
-Djava.net.preferIPv4Stack=true"
        export JAVA_OPTIONS
目前的版本是需要IPV4来实现,IPv6不可以,所以要明确指出IPv4,屏蔽IPv6

 

以上是关于welogic的受管理服务器无法启动的主要内容,如果未能解决你的问题,请参考以下文章

无法访问派生类中的受保护方法

无法访问基类中的受保护成员 [重复]

Identity Server 4 无法验证来自 localhost 的受保护 API 的令牌

无法访问派生类中基类的受保护成员

静态成员函数无法访问类的受保护成员

如何从片段适配器启动活动