`

Weblogic Cluster BEA-000116故障处理

 
阅读更多

部署环境:Weblogic 10 MP2 for UNIX
实验:
Weblogic Cluster: (MServer1,MServer2) 7222
Multicast IP: 239.192.0.0
AdminServer: 192.168.1.33:7001
MServer1: 192.168.1.33:7201
MServer2: 192.168.1.33:7202
Machine1: (MServer1) NodeManager(192.168.1.33:5556)
Machine2: (MServer2) NodeManager(192.168.1.33:5557)
注意:本实验环境各个Server SSL设置---->Hostname Verification: NONE
描述:
(NodeManager 成功启动)
当启动某ManagedServer时分别报以下错误:
/home/weblogic/bea/user_projects/domains/clustersys/servers/MServer_1/logs/MServer_1.out
Dec 16, 2010 9:12:56 PM CST> <Info> <WebLogicServer> <BEA-000215>
<Loaded License : /home/weblogic/bea/license.bea>
<Dec 16, 2010 9:12:57 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 16, 2010 9:12:57 PM CST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Dec 16, 2010 9:12:58 PM CST> <Notice> <Log Management> <BEA-170019> <The server log file
<Dec 16, 2010 9:13:15 PM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Dec 16, 2010 9:13:31 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Dec 16, 2010 9:13:31 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>


<Dec 16, 2010 9:13:34 PM CST> <Error> <Cluster> <BEA-000116>
<Failed to join cluster Cluster_1 at address 239.192.0.0 due to: java.net.SocketException:
No such device.java.net.SocketException:
No such device

at java.net.PlainDatagramSocketImpl.join(Native Method)
at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:172)
at java.net.MulticastSocket.joinGroup(MulticastSocket.java:276)
at weblogic.cluster.MulticastFragmentSocket.initializeMulticastSocket(MulticastFragmentSocket.java:112)
at weblogic.cluster.MulticastFragmentSocket.start(MulticastFragmentSocket.java:134)
Truncated. see log file for complete stacktrace
>
<Dec 16, 2010 9:13:34 PM CST> <Critical> <WebLogicServer> <BEA-000362>
<Server failed. Reason: There are 1 nested errors:
java.net.SocketException: No such device
at java.net.PlainDatagramSocketImpl.join(Native Method)
at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:172)
at java.net.MulticastSocket.joinGroup(MulticastSocket.java:276)
at weblogic.cluster.MulticastFragmentSocket.initializeMulticastSocket(MulticastFragmentSocket.java:112)
at weblogic.cluster.MulticastFragmentSocket.start(MulticastFragmentSocket.java:134)
at weblogic.cluster.FragmentSocketWrapper.start(FragmentSocketWrapper.java:87)
at weblogic.cluster.MulticastManager$1.run(MulticastManager.java:186)
at weblogic.cluster.MulticastManager.startListening(MulticastManager.java:192)
at weblogic.cluster.InboundService.startListening(InboundService.java:40)
at weblogic.cluster.InboundService.start(InboundService.java:29)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
<Dec 16, 2010 9:13:34 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Dec 16, 2010 9:13:34 PM CST> <Error> <WebLogicServer> <BEA-000383>
<A critical service failed. The server will shut itself down>
<Dec 16, 2010 9:13:34 PM CST> <Notice> <WebLogicServer> <BEA-000365>
<Server state changed to FORCE_SHUTTING_DOWN>
<Dec 16, 2010 9:13:37 PM> <Debug> <NodeManager> <Waiting for the process to die: 26869>
<Dec 16, 2010 9:13:38 PM> <Info> <NodeManager> <Server failed during startup so will not be restarted>
<Dec 16, 2010 9:13:38 PM> <Debug> <NodeManager>
<runMonitor returned, setting finished=true and notifying waiters>

AdminServer 前台报以下信息:

<Dec 16, 2010 9:13:40 PM CST> <Error> <NodeManager> <BEA-300048> <Unable to start the server MServer_1 :
Exception while starting server 'MServer_1': java.io.IOException: Server failed to start up.
See server output log for more details.>

分析:依据以下提示,可判断组播地址问题。

Dec 16, 2010 9:13:34 PM CST> <Error> <Cluster> <BEA-000116> <Failed to join cluster Cluster_1
at address 239.192.0.0 due to: java.net.SocketException: No such device.

查看系统路由表:
[root@localhost ~]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0

缺一条组播239.192.0.0路由
手动添加路由:
[root@localhost ~]# route add -host 239.192.0.0 dev eth0
[root@localhost ~]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
239.192.0.0 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0

再启动受控服务器,OK


同样的原因也会导致以下异常抛出:
注意:1. 本实验环境各个Server SSL设置---->Hostname Verification:: BEA HOSTNAME Verifier
2. Weblogic 11gr3(10.3) 不适合此环境
基于SSL环境下 ,成功启动节点管理器后,受控服务器无法正常启动
现象:
当启动MServer_1时,服务器状态:
MServer_1   Machine_1   FAILED_NOT_RESTARTABLE    FAILED
NodeManager 报错:
Dec 16, 2010 11:23:54 PM> <INFO> <clustersys> <States = {MServer_2=UNKNOWN, AdminServer=UNKNOWN, MServer_1=UNKNOWN, domain_bak=UNKNOWN}>
<Dec 16, 2010 11:23:54 PM> <INFO> <clustersys> <States = {MServer_2=UNKNOWN, AdminServer=UNKNOWN, MServer_1=UNKNOWN, domain_bak=UNKNOWN}>
<Dec 16, 2010 11:23:57 PM> <INFO> <clustersys> <States = {MServer_2=UNKNOWN, AdminServer=UNKNOWN,

<Dec 16, 2010 11:23:57 PM> <Info> <clustersys> <MServer_1>
<Dec 16, 2010 11:23:57 PM> <Info> <clustersys> <MServer_1> <Startup configuration properties saved to "/home/weblogic/bea/user_projects/domains/clustersys/servers/MServer_1/data/nodemanager/startup.properties">
<Dec 16, 2010 11:23:57 PM> <Info> <clustersys> <MServer_1> <Rotated server output log to "/home/weblogic/bea/user_projects/domains/clustersys/servers/MServer_1/logs/MServer_1.out00005">
<Dec 16, 2010 11:23:57 PM> <Info> <clustersys> <MServer_1> <Server error log also redirected to server log>

<Dec 16, 2010 11:26:44 PM> <Info> <clustersys> <MServer_1> <Server failed during startup so will not be restarted>
<Dec 16, 2010 11:26:44 PM> <Warning> <Exception while starting server 'MServer_1': java.io.IOException: Server failed to start up. See server output log for more details.>
java.io.IOException: Server failed to start up. See server output log for more details.
        at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:303)
        at weblogic.nodemanager.server.Handler.handleStart(Handler.java:542)
        at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
        at weblogic.nodemanager.server.Handler.run(Handler.java:66)
        at java.lang.Thread.run(Thread.java:595)
<Dec 16, 2010 11:28:18 PM> <INFO> <clustersys> <States = {MServer_2=UNKNOWN, AdminServer=UNKNOWN, MServer_1=FAILED_NOT_RESTARTABLE, domain_bak=UNKNOWN}>

控制台:
<Dec 16, 2010 11:26:44 PM CST>  <Error> <NodeManager> <BEA-300048> <Unable to start the server MServer_1 : Exception while starting server 'MServer_1': java.io.IOException: Server failed to start up. See server output log for more details.>
查看日志,分析原因:
/home/weblogic/bea/user_projects/domains/clustersys/servers/MServer_1/logs/MServer_1.out
<Dec 16, 2010 11:26:36 PM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Dec 16, 2010 11:26:42 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Dec 16, 2010 11:26:42 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>

<Dec 16, 2010 11:26:43 PM CST>  <Error> <Cluster> <BEA-000116> <Failed to join cluster Cluster_1 at address 239.192.0.0 due to :

java.net.SocketException: No such device
        at java.net.PlainDatagramSocketImpl.join(Native Method)
        at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:172)
        at java.net.MulticastSocket.joinGroup(MulticastSocket.java:276)
        at weblogic.cluster.MulticastFragmentSocket.initializeMulticastSocket(MulticastFragmentSocket.java:112)
        at weblogic.cluster.MulticastFragmentSocket.start(MulticastFragmentSocket.java:134)
        Truncated. see log file for complete stacktrace
>
<Dec 16, 2010 11:26:43 PM CST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: There are 1 nested errors:
 
java.net.SocketException: No such device
        at java.net.PlainDatagramSocketImpl.join(Native Method)
        at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:172)
        at java.net.MulticastSocket.joinGroup(MulticastSocket.java:276)
        at weblogic.cluster.MulticastFragmentSocket.initializeMulticastSocket(MulticastFragmentSocket.java:112)
        at weblogic.cluster.MulticastFragmentSocket.start(MulticastFragmentSocket.java:134)
        at weblogic.cluster.FragmentSocketWrapper.start(FragmentSocketWrapper.java:87)
        at weblogic.cluster.MulticastManager$1.run(MulticastManager.java:186)
        at weblogic.cluster.MulticastManager.startListening(MulticastManager.java:192)
        at weblogic.cluster.InboundService.startListening(InboundService.java:40)
        at weblogic.cluster.InboundService.start(InboundService.java:29)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
<Dec 16, 2010 11:26:43 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Dec 16, 2010 11:26:43 PM CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Dec 16, 2010 11:26:43 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Dec 16, 2010 11:26:44 PM> <Debug> <NodeManager> <Waiting for the process to die: 4428>
<Dec 16, 2010 11:26:44 PM> <Info> <NodeManager> <Server failed during startup so will not be restarted>
<Dec 16, 2010 11:26:44 PM> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>

解决方法同上,手动添加组播路由

参考至:http://www.day-up.com/index.php?ac=article&at=read&did=305
如有错误,欢迎指正
邮箱:czmcj@163.com

分享到:
评论

相关推荐

    实战集锦_WebLogic Server Cluster组播故障处理总结

    ### WebLogic Server Cluster组播故障处理总结 #### 问题描述 在使用WebLogic Server Cluster时,可能会遇到实例在监听或接收消息时出现问题的情况,尤其是在BEA WebLogic Server之间使用组播功能时出现通信失败的...

    BEA WebLogic Cluster

    ### BEA WebLogic Cluster 关键知识点 #### 一、引言与路线图 - **文档范围及受众**:本文档旨在介绍 BEA WebLogic Server 集群的使用方法,适用于那些希望了解集群如何工作以及如何配置集群以提高应用程序性能和...

    BEA-Weblogic-config

    ### 关于BEA WebLogic Server 10.0配置向导的理解与应用 #### 一、引言 BEA WebLogic Server是一款高级的企业级应用程序服务器,由BEA Systems开发并维护,现已被Oracle公司收购。它支持Java EE标准,提供了一个...

    weblogic cluster configuration

    在 WebLogic Server 10.0 版本中,BEA 对集群功能进行了显著增强,包括但不限于改进的负载均衡策略、增强的故障转移机制以及更灵活的集群管理选项等。 #### 二、理解 WebLogic Server 集群 ##### 什么是 WebLogic ...

    WebLogic 9.0 Command Reference

    《WebLogic Server Command Reference》是针对BEA Systems, Inc.发布的WebLogic Server 9.0版本的官方命令手册。本书详细介绍了如何通过命令行方式管理和操作WebLogic Server,旨在帮助系统管理员、开发者以及任何与...

    weblogic集群配置方法-具体实施步骤.doc

    /home/weblogic/bea/bin/config.sh -mode=console -template=domain -name=myClusterDomain -clusterName=myCluster -adminUrl=t3://localhost:7001 ``` 这将在每个主机上创建一个新的域目录,如`/home/...

    Weblogic基础管理新视频教程.txt

    - **版本历史**:了解WebLogic Server的发展历程,包括其从最早的BEA Systems到被Oracle收购后的发展变化。 - **安装步骤**:详细介绍如何在不同的操作系统(如Windows、Linux等)上安装WebLogic Server,并介绍安装...

    BEA的weblogic和tuxedo

    "Cluster.ppt"可能介绍了WebLogic集群的概念和配置,集群可以提高系统的可用性和可扩展性,通过在多个服务器之间共享工作负载来实现故障转移和负载均衡。WebLogic的集群特性使得企业在面临高流量或单点故障时,能够...

    Weblogic加Apache的负载均衡以及群集配置[借鉴].pdf

    - 修改Apache的主配置文件`httpd.conf`,加载`mod_wl_22.so`模块,并配置WebLogic Cluster的相关参数,如服务器地址、日志位置、调试选项等。 4. **部署应用程序**: - 登录WebLogic管理控制台,在Machine2的...

    weblogic基础知识介绍

    - **定义**: BEA WebLogic Server提供的基于Web的图形用户界面,用于管理WebLogic Server域。 - **功能**: 包括配置服务器实例、服务、安全参数、应用程序部署与管理等。 - **访问**: 通过任何支持的Web浏览器...

    WEBLOGIC集群

    **WebLogic**是由美国BEA公司(现已被Oracle收购)开发的一款基于Java EE架构的企业级应用服务器,它不仅是一个应用服务器,还是一个功能全面的中间件平台,提供了一系列企业级特性,包括高性能、高可用性、可扩展性...

    Weblogic单服务器集群

    采用两个WebLogic Server集群,一个用于处理静态内容和集群Servlet,另一个用于处理集群EJB。适用于以下情况: - 当负载平衡机制需要调用集群EJB中的方法时; - 当需要在提供内容与提供对象的服务间保持更大灵活性...

    BEA dev2dev WebLogic管理精华

    ogic 中的 Cluster 和复制功能详解...............................................................................152.6 如何处理应用部署时的 Classpath 冲突问题?.............................................

    weblogic

    这个压缩包文件包含了一系列与WebLogic相关的培训资料,由BEA的专业讲师精心制作,适合对WebLogic感兴趣的初学者和进阶者学习。 03-WLA-Slides.pdf可能涵盖了WebLogic Administration的基础知识,包括WebLogic ...

    weblogic集群测试.pdf

    在httpd.conf文件中,需要加载WebLogic模块,并定义相关的模块配置指令,如LoadModule和WebLogicCluster指令。WebLogicCluster指令定义了集群中所有节点的IP和端口号,以便Apache可以将请求正确地分发到各个节点。...

    WebLogic8 Server03集群配置

    WebLogic Server 集群允许将多个服务器实例组合成一个逻辑单元,以实现负载均衡、故障转移和资源共享。以下是关于WebLogic Server 8.1.4集群配置的详细知识点: ### 1. 集群环境配置 - **平台**: 在Windows 2003 ...

    Linux下Weblogic9集群配置

    在Weblogic 9的集群配置中,通常会分为两层:一层处理静态内容和Servlet的集群,另一层处理EJB(Enterprise JavaBeans)的集群。这种设计在需要负载均衡、内容和服务之间灵活切换以及提高系统稳定性的情况下特别适用...

    BEA集群资料PPT

    BEA(现在已被Oracle公司收购,更名为Oracle WebLogic Server)是一款企业级的应用服务器,它提供了一种强大的集群解决方案,能够提高应用程序的可用性、可伸缩性和性能。集群是通过将多个独立的服务器实例组合在...

    weblogic集群设置

    集群配置是其关键特性之一,通过将多个WebLogic Server实例组合成一个集群,可以实现应用的高可用性、负载均衡和故障转移,从而提高系统的稳定性和响应速度。 **二、WebLogic集群架构详解** ### 2.1 单层混合型...

Global site tag (gtag.js) - Google Analytics