https://bz.apache.org/bugzilla/show_bug.cgi?id=64658
--- Comment #6 from Felix Schumacher <[email protected]> --- If you are using a current version of OpenJDK (or a commercially licensed Oracle JDK), you can enable the flight recorder and look into the state of the JVM afterwards. You could add the following line to your bin/setenv.bat (or bin/setenv.sh under linux) to enable the flight recorder and save the events in a file named recording.jfr JVM_ARGS="-XX:StartFlightRecording=disk=true,dumponexit=true,filename=recording.jfr,maxsize=1024m,maxage=1d,settings=profile,path-to-gc-roots=true" (Note I have tried this under linux, only) The recording can be analysed with the tool Mission Control (which can be downloaded from the AdoptOpenJDK and other places). If you are not afraid to send the recording data to me, I could take a look into it. Another trick you could try is to look at the network connections JMeter is trying to open on startup (it shouldn't open any on it's own, but the plugins might do so) with a windows system monitoring tool you like. -- You are receiving this mail because: You are the assignee for the bug.
