Jmeter perfmon :EXCEPTION_ACCESS_VIOLATION

0

I am trying to run a performance test of my server using jmeter perfmon plugin. But I am getting an error as in the following image. I have searched a lot for a solution but couldn't find an answer. I tried setting JVM arguments but it didn't work. Link to error image.How can I get it worked?

INFO    2019-12-30 14:11:25.114 [kg.apc.p] (): Binding UDP to 4444
INFO    2019-12-30 14:11:25.155 [kg.apc.p] (): Binding TCP to 4444
INFO    2019-12-30 14:11:25.161 [kg.apc.p] (): JP@GC Agent v2.2.3 started
INFO    2019-12-30 14:11:37.974 [kg.apc.p] (): Accepting new TCP connection
INFO    2019-12-30 14:11:37.978 [kg.apc.p] (): Yep, we received the 'test' command
INFO    2019-12-30 14:11:37.979 [kg.apc.p] (): Starting measures: memory:       cpu:
A fatal error has been detected by the Java Runtime Environment:
EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000010014ed4, pid=12236, tid=6844
JRE version: Java(TM) SE Runtime Environment (11.0.4+10) (build 11.0.4+10-LTS)
Java VM: Java HotSpot(TM) 64-Bit Server VM (11.0.4+10-LTS, mixed mode, tiered, compressed oops, g1 
gc, windows-amd64)
Problematic frame:
C  [sigar-amd64-winnt.dll+0x14ed4]
No core dump will be written. Minidumps are not enabled by default on client versions of Windows

An error report file with more information is saved as:
E:\\hs_err_pid12236.log

If you would like to submit a bug report, please visit:
http://bugreport.java.com/bugreport/crash.jsp
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.
performance
jmeter
load-testing
qa
asked on Stack Overflow Dec 30, 2019 by Sebin Vincent

1 Answer

1

Looking into JVM crashes occassionally with access violation when using Sigar.getProcMem with disabled Windows performance counters #77 issue it might be the case that Windows don't have performance counters enabled hence Sigar fails to query the CPU status from Windows PerfMon

  1. Check if CPU (and other stats) are exposed in PerfMon
  2. Try running Powershell and Server Agent as Administrator
  3. Try using cmd.exe interpreter instead of powershell
  4. Try running ServerAgent.bat --sysinfo to see if there are any errors there
  5. Inspect e:\hs_err_pid12236.log file for any clues

If nothing helps be aware that you can use SSHMon plugin for server monitoring, it doesn't require server-side software installation

answered on Stack Overflow Dec 30, 2019 by Dmitri T

User contributions licensed under CC BY-SA 3.0