Question

我收到以下错误....请帮助

[8/5/14 21:06:54:277 GMT-08:00] 00000091 DiscoveryTx   W   DCSV1115W: DCS Stack DefaultCoreGroup at Member PT_STS_HK_CELL\PT_STS_HK_APP_Node02\PT_STS_QLCOMM_CL02: Member PT_STS_HK_CELL\PT_STS_HK_APP_Node02\nodeagent connection  was closed. Member will  be removed from view. DCS connection status is Discovery|Ptp, transmitter closed.
[8/5/14 21:07:23:562 GMT-08:00] 00000010 MbuRmmAdapter W   DCSV1115W: DCS Stack DefaultCoreGroup at Member PT_STS_HK_CELL\PT_STS_HK_APP_Node02\PT_STS_QLCOMM_CL02: Member PT_STS_HK_CELL\PT_STS_HK_APP_Node02\PT_STS_PYMTCAPTURE_CL02 connection  was closed. Member will  be removed from view. DCS connection status is View|Gossip, this member is suspected by the other member.
[8/5/14 21:08:00:079 GMT-08:00] 00000091 DiscoveryTx   W   DCSV1115W: DCS Stack DefaultCoreGroup at Member PT_STS_HK_CELL\PT_STS_HK_APP_Node02\PT_STS_QLCOMM_CL02: Member PT_STS_HK_CELL\PT_STS_HK_APP_Node02\PT_STS_DOWNSTREAM_CL02 connection  was closed. Member will  be removed from view. DCS connection status is Discovery|Ptp, transmitter closed.
[8/5/14 21:08:16:296 GMT-08:00] 00000010 RmmPtpGroup   W   DCSV1112W: DCS Stack DefaultCoreGroup at Member PT_STS_HK_CELL\PT_STS_HK_APP_Node02\PT_STS_QLCOMM_CL02: Member PT_STS_HK_CELL\PT_STS_HK_APP_Node02\PT_STS_DOWNSTREAM_CL02 failed to respond to periodic heartbeats. Member will be removed from view. Configured Timeout is 180000 milliseconds. DCS logical channel is View|Ptp.
[8/5/14 21:08:29:236 GMT-08:00] 00000091 DiscoveryTx   W   DCSV1115W: DCS Stack DefaultCoreGroup at Member PT_STS_HK_CELL\PT_STS_HK_APP_Node02\PT_STS_QLCOMM_CL02: Member PT_STS_HK_CELL\PT_STS_HK_DMGR_Node\dmgr connection  was closed. Member will  be removed from view. DCS connection status is Discovery|Ptp, transmitter closed.
[8/5/14 21:10:20:892 GMT-08:00] 00000018 ApplicationMo W   DCSV0004W: DCS Stack DefaultCoreGroup at Member PT_STS_HK_CELL\PT_STS_HK_APP_Node02\PT_STS_QLCOMM_CL02: Did not receive adequate CPU time slice. Last known CPU usage time at 21:03:08:272 GMT-08:00. Inactivity duration was 402 seconds. 
[8/5/14 21:11:14:131 GMT-08:00] 00000043 ThreadMonitor W   WSVR0605W: Thread "WMQJCAResourceAdapter : 5" (00000067) has been active for 657039 milliseconds and may be hung.  There is/are 2 thread(s) in total in the server that may be hung.
    at com.ibm.ejs.ras.TraceLogger.doLog(TraceLogger.java:332)
    at com.ibm.ejs.ras.TraceLogger.processEvent(TraceLogger.java:319)
    at com.ibm.ws.logging.WsHandlerWrapper.publish(WsHandlerWrapper.java:43)
    at java.util.logging.Logger.log(Logger.java:1121)
    at com.ibm.ejs.ras.Tr.logToJSR47Logger(Tr.java:1681)
    at com.ibm.ejs.ras.Tr.fireEvent(Tr.java:1643)
    at com.ibm.ejs.ras.Tr.fireTraceEvent(Tr.java:1565)
    at com.ibm.ejs.ras.Tr.entry(Tr.java:816)
    at com.ibm.ws.sib.utils.ras.SibTr.entry(SibTr.java:912)
    at com.ibm.ws.wmqcsi.trace.TraceImpl.methodExit(TraceImpl.java:349)
    at com.ibm.msg.client.commonservices.trace.Trace.methodExitInternal(Trace.java:715)
    at com.ibm.msg.client.commonservices.trace.Trace.exit(Trace.java:628)
    at com.ibm.msg.client.wmq.v6.jms.internal.JMSMessage._setJMSXObjectProperty(JMSMessage.java:3928)
    at com.ibm.msg.client.wmq.v6.jms.internal.MQJMSMessage.write(MQJMSMessage.java:1223)
    at com.ibm.msg.client.wmq.v6.jms.internal.MQMessageProducer.sendInternal(MQMessageProducer.java:1139)
    at com.ibm.msg.client.wmq.v6.jms.internal.MQMessageProducer.send(MQMessageProducer.java:768)
    at com.ibm.msg.client.wmq.v6.jms.internal.MQMessageProducer.send(MQMessageProducer.java:2713)
    at com.ibm.msg.client.jms.internal.JmsMessageProducerImpl.sendMessage(JmsMessageProducerImpl.java:872)
    at com.ibm.msg.client.jms.internal.JmsMessageProducerImpl.send_(JmsMessageProducerImpl.java:727)
    at com.ibm.msg.client.jms.internal.JmsMessageProducerImpl.send(JmsMessageProducerImpl.java:398)
    at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:281)
    at com.ibm.ejs.jms.JMSQueueSenderHandle.send(JMSQueueSenderHandle.java:204)

Answer 1

您收到的CPU Starvation错误。这可能是因为你正在捣乱垃圾收集器，你的堆不够大或者其他东西占用了CPU时间。您需要找到占用CPU的进程或进程，并检查它们运行高的原因。

此致布赖恩

Answer 2

以

开头的日志条目

ThreadMonitor W WSVR0605W: Thread "WMQJCAResourceAdapter : 5" (00000067) has been 
active for 657039 milliseconds and may be hung.

表示此线程在该段时间内处于活动状态，但它生成的线程堆栈只是生成日志条目的时间点的线程。这意味着它可能在代码中的一个点上停留了90％，并且生成的堆栈跟踪就在现在的位置。

当该应用程序尝试发送MQ JMS消息时，该特定线程正在执行的操作是在跟踪日志中附加一个条目。所以没有迹象表明该线程在那时挂起。

要尝试的几件事情：

调查CPU使用率，因为CPU饥饿消息表明这是一个问题。
在SystemOut.log中搜索相应的消息，说明线程不再挂起。
拿一个javacore以2分钟的间隔查看线程，看看哪些线程正在移动。
除非您需要，否则请关闭跟踪。

Answer 3

这是服务器启动阶段可能遇到的一般错误。

这背后的基本思想是，当您启动服务器时，会为您要在服务器上运行的进程/作业初始化线程。该线程正在等待几个资源，这有助于他们运行进程/作业。但是在那个时候，由于资源不可用，线程可能会挂起。

解决此问题的一种方法 - 从背景中删除进程，因为该线程已挂起。再次启动服务器。

Answer 4

执行以下步骤： - 确保Deployment Manager已启动并正在运行 - 验证应用服务器和节点代理是否已停止 - 没有与节点代理和应用服务器运行相关的Java进程 - 转到NODE_PROFILE \ bin（不是部署管理器配置文件） - 运行 syncNode.sh/bat - 运行startNode.sh/bat - 如果节点代理成功启动，您应该能够从命令行或Web控制台启动服务器

可能挂起的Websphere服务器

4 个答案: