WAS startnode hang问题解决
WAS startnode hang问题解决
[@more@]WAS的集群环境,假设192.168.1.10为A机 192.168.1.20为B机,A、B两机做Cluster,Dmger在A机。因为春节下电,开机时现象是,Dmger正常,B机上的Node正常启动,但是A机上的Node启动时,出现“”后,无响应,查询系统启动日志,无记录。
检查一下操作系统的状态,内存、磁盘空间一切正常。ps -ef|grep java系统进程也在。
咨询800,只是让按要求收集信息:
http://www-1.ibm.com/support/docview.wss?rs=180&context=SSCMPB9&q1=MustGatherDocument&uid=swg21052641&loc=en_US&cs=utf-8&lang=enhttp://www-1.ibm.com/support/docview.wss?uid=swg21201014
打开trace查看node启动的问题记录:
#startNode.sh -trace
从系统日志中无法看出系统异常。
于是联想到去年曾经在配置结点时federate异常,最后是因为JVM的share memory问题造成。最后IBM建议按该问题处理。
1、启动dmgr,在管理控制台系统管理中,选择无法启动的那个nodeagent,在进程管理->进程定义->java虚拟机 的通用jvm参数里添加“-Xshareclasses:nonfatal”,保存。 2、在无法启动的节点的bin下执行syncNode命令,强制节点配置于dmgr同步,同步后查看configcellsnodesserversnodeagentserver.xml, 3、启动nodeagent。 |
设置后,重启Dmgr和Node后,Node正常启动!据说WAS 6109会对share classes问题修正。
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/7199667/viewspace-1034960/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/7199667/viewspace-1034960/
- 点赞
- 收藏
- 分享
- 文章举报
- 解决Server Tomcat v8.0 Server at localhost was unable to start within 45 seconds.问题
- 解决Server Tomcat v7.0 Server at localhost was unable to start within 45 seconds.问题
- Server Tomcat v7.0 Server at localhost was unable to start within 45 seconds问题解决
- 记录一次eclipse的错误:“server tomcat v7.0 server at localhost was unable to start within 45 seconds”的问题解决思路
- 解决tomcat启动时erver Tomcat Server at localhost was unable to start within 45 seconds
- linux下安装node出现的node命令找不到,express命令找不到的问题,解决方法。
- node——响应数据类型 Content-Type(解决中文乱码问题)
- 解决“The superclass "javax.servlet.http.HttpServlet" was not found on the Java Build Path”问题
- hive的Specified key was too long; max key length is 767 bytes问题解决
- Could not create the view: An unexpected exception was thrown.问题解决
- Could not create the view: An unexpected exception was thrown.问题解决
- 解决Azure publish “the remote desktop configuration was not generated by windows azure Tools”问题
- 针对报出 cvc-complex-type.2.4.a: Invalid content was found starting with element 问题解决办法
- 解决JMail发送邮件报错The message was undeliverable. All servers failed to receive the message的问题
- Mac下node.js的安装配置及问题解决
- 安装Grid Control , OPMN Process Manager failed to start 问题解决
- 转--Could not create the view: An unexpected exception was thrown.问题解决
- 解决node、npm 安装缺libicu18.so.48 问题
- failed to lazily initialize a collection of role: no session or session was closed (Hibernate) 解决方法(延迟加载问题)
- apktool 反编译 Input file was not found or was not readable.问题解决方案