【Weblogic集群】Weblogic Cluster BEA-000116故障处理经验

2023-10-11 19:32

本文主要是介绍【Weblogic集群】Weblogic Cluster BEA-000116故障处理经验,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

原文来自:http://www.day-up.com/index.php?ac=article&at=read&did=305

部署环境: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

http://blog.csdn.net/frist_huangsuli/article/details/7731615

这篇关于【Weblogic集群】Weblogic Cluster BEA-000116故障处理经验的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/190350

相关文章

Redis分片集群的实现

《Redis分片集群的实现》Redis分片集群是一种将Redis数据库分散到多个节点上的方式,以提供更高的性能和可伸缩性,本文主要介绍了Redis分片集群的实现,具有一定的参考价值,感兴趣的可以了解一... 目录1. Redis Cluster的核心概念哈希槽(Hash Slots)主从复制与故障转移2.

Python FastAPI+Celery+RabbitMQ实现分布式图片水印处理系统

《PythonFastAPI+Celery+RabbitMQ实现分布式图片水印处理系统》这篇文章主要为大家详细介绍了PythonFastAPI如何结合Celery以及RabbitMQ实现简单的分布式... 实现思路FastAPI 服务器Celery 任务队列RabbitMQ 作为消息代理定时任务处理完整

C#使用SQLite进行大数据量高效处理的代码示例

《C#使用SQLite进行大数据量高效处理的代码示例》在软件开发中,高效处理大数据量是一个常见且具有挑战性的任务,SQLite因其零配置、嵌入式、跨平台的特性,成为许多开发者的首选数据库,本文将深入探... 目录前言准备工作数据实体核心技术批量插入:从乌龟到猎豹的蜕变分页查询:加载百万数据异步处理:拒绝界面

Springboot处理跨域的实现方式(附Demo)

《Springboot处理跨域的实现方式(附Demo)》:本文主要介绍Springboot处理跨域的实现方式(附Demo),具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不... 目录Springboot处理跨域的方式1. 基本知识2. @CrossOrigin3. 全局跨域设置4.

python+opencv处理颜色之将目标颜色转换实例代码

《python+opencv处理颜色之将目标颜色转换实例代码》OpenCV是一个的跨平台计算机视觉库,可以运行在Linux、Windows和MacOS操作系统上,:本文主要介绍python+ope... 目录下面是代码+ 效果 + 解释转HSV: 关于颜色总是要转HSV的掩膜再标注总结 目标:将红色的部分滤

Python实现自动化接收与处理手机验证码

《Python实现自动化接收与处理手机验证码》在移动互联网时代,短信验证码已成为身份验证、账号注册等环节的重要安全手段,本文将介绍如何利用Python实现验证码的自动接收,识别与转发,需要的可以参考下... 目录引言一、准备工作1.1 硬件与软件需求1.2 环境配置二、核心功能实现2.1 短信监听与获取2.

Python使用date模块进行日期处理的终极指南

《Python使用date模块进行日期处理的终极指南》在处理与时间相关的数据时,Python的date模块是开发者最趁手的工具之一,本文将用通俗的语言,结合真实案例,带您掌握date模块的六大核心功能... 目录引言一、date模块的核心功能1.1 日期表示1.2 日期计算1.3 日期比较二、六大常用方法详

利用Go语言开发文件操作工具轻松处理所有文件

《利用Go语言开发文件操作工具轻松处理所有文件》在后端开发中,文件操作是一个非常常见但又容易出错的场景,本文小编要向大家介绍一个强大的Go语言文件操作工具库,它能帮你轻松处理各种文件操作场景... 目录为什么需要这个工具?核心功能详解1. 文件/目录存javascript在性检查2. 批量创建目录3. 文件

Java使用多线程处理未知任务数的方案介绍

《Java使用多线程处理未知任务数的方案介绍》这篇文章主要为大家详细介绍了Java如何使用多线程实现处理未知任务数,文中的示例代码讲解详细,感兴趣的小伙伴可以跟随小编一起学习一下... 知道任务个数,你可以定义好线程数规则,生成线程数去跑代码说明:1.虚拟线程池:使用 Executors.newVir

一文带你深入了解Python中的GeneratorExit异常处理

《一文带你深入了解Python中的GeneratorExit异常处理》GeneratorExit是Python内置的异常,当生成器或协程被强制关闭时,Python解释器会向其发送这个异常,下面我们来看... 目录GeneratorExit:协程世界的死亡通知书什么是GeneratorExit实际中的问题案例