我的perfMon插件总是在6秒后停止监视服务器的运行情况。perfMon图
我正在使用:
在我的客户端和服务器站之间有一个成功的连接,首先收集度量,但总是发生错误:
信息2022-09-02 22:00:50.882 kg.apc.p:将UDP绑定到4444
信息2022-09-02 22:00:51.882 kg.apc.p:将TCP绑定到4444
信息2022-09-02 22:00:51.882 kg.apc.p:JP@GC代理v2.2.0启动
信息2022-09-02 22:01:04.713 kg.apc.p:接受新的TCP连接
信息2022-09-02 22:01:31.092 kg.apc.p:接受新的TCP连接
信息2022-09-02 22:01:31.108 kg.apc.p:是的,我们收到了“测试”命令
信息2022-09-02 22:01:31.889 kg.apc.p:启动措施: cpu:内存:
错误2022-09-02 22:02:22.744 kg.apc.p:从网络层读取错误
java.io.IOException:现有连接被远程主机强制关闭
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(Unknown Source)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
at sun.nio.ch.IOUtil.read(Unknown Source)
at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
at kg.apc.perfmon.PerfMonWorker.read(PerfMonWorker.java:181)
at kg.apc.perfmon.PerfMonWorker.processCommands(PerfMonWorker.java:97)
at kg.apc.perfmon.AgentTool.processParams(AgentTool.java:72)
at kg.apc.cmdtools.PluginsCMD.processParams(PluginsCMD.java:63)
at kg.apc.cmdtools.PluginsCMD.processParams(PluginsCMD.java:23)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at kg.apc.cmd.UniversalRunner.main(UniversalRunner.java:175)错误2022-09-02 22:02:23.635 kg.apc.p:无法向TCP网络连接发送数据
java.io.IOException:现有连接被远程主机强制关闭
at sun.nio.ch.SocketDispatcher.write0(Native Method)
at sun.nio.ch.SocketDispatcher.write(Unknown Source)
at sun.nio.ch.IOUtil.writeFromNativeBuffer(Unknown Source)
at sun.nio.ch.IOUtil.write(Unknown Source)
at sun.nio.ch.SocketChannelImpl.write(Unknown Source)
at kg.apc.perfmon.PerfMonWorker.processSenders(PerfMonWorker.java:281)
at kg.apc.perfmon.PerfMonWorker.run(PerfMonWorker.java:243)
at java.lang.Thread.run(Unknown Source)我在寻找一些线索,但我没有找到: D,你认为这里的问题是什么?
提前感谢你们的帮助!
发布于 2022-09-02 14:43:47
如果您看到以下内容,请查看您的服务器代理控制台:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000000bd4ed4, pid=25076, tid=0x0000000000004674
#
# JRE version: Java(TM) SE Runtime Environment (8.0_261-b12) (build 1.8.0_261-b12)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.261-b12 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [sigar-amd64-winnt.dll+0x14ed4]这意味着您正在遭受SIGAR bug 136的困扰,这意味着您要么需要重新编译sigar-amd64-winnt.dll,要么采用固定版本,即从这里中替换服务器代理安装的"lib“文件夹中的版本。
也要注意,有ServerAgent-2.2.3、JMeter 5.5和根据JMeter最佳实践,您应该始终使用最新版本的JMeter,所以可能值得考虑升级。
https://stackoverflow.com/questions/73582508
复制相似问题