https://bz.apache.org/bugzilla/show_bug.cgi?id=65000
--- Comment #8 from Madhuri Jain <[email protected]> --- (In reply to Madhuri Jain from comment #7) The issue of thread dump is resolved by using pid from jps. # jps -l 128 /jmeter/apache-jmeter-5.4/bin/ApacheJMeter.jar # jcmd 128 Thread.print #### WORKED ##### I'm trying to reproduce the issue and will provide the required thread dump once it occurs. Thanks! > (In reply to Madhuri Jain from comment #6) > To add more details: > I'm issuing the command as root user and the process is also running by root. > > # whoami > root > # ps > PID USER TIME COMMAND > 54 root 0:00 {jmeter.sh} /bin/sh > /jmeter/apache-jmeter-5.4/bin/jmeter.sh -s -Jbeanshell.server.port=9000 > 70 root 0:00 {jmeter} /bin/sh /jmeter/apache-jmeter-5.4/bin/jmeter > -s -Jbeanshell.server.port=9000 > > (Though I'm bit confused why it shows 2 jmeter processes) > > > (In reply to Philippe Mouawad from comment #5) > > Hello, > > Thank you for the useful insight and apologies for delay. > > > > I had been trying to reproduce the issue, but seems like it's not getting > > reproduced again. I'd get back with the details as soon as this gets > > reproduced on the setup. > > > > To dig further, can I please get some more details on the following: > > > > 1. Timeouts - Is there a recommended way to set default timeouts and control > > this behavior for all test plans run on a JMeter setup (distributed), > > through properties like httpclient.timeout and would it suffice? > > > > 2. Thread dump - I've changed the image to > > mcr.microsoft.com/java/jdk:15-zulu-alpine > > (Link: https://hub.docker.com/_/microsoft-java-jdk) > > > > Here're the errors I'm getting with different commands: > > > > jstack -l -e 71 > > 71: Unable to open socket file /proc/71/root/tmp/.java_pid71: target process > > 71 doesn't respond within 10500ms or HotSpot VM not loaded > > > > jstack -l -e -F 71 > > Error: -F option used > > Cannot connect to core dump or remote debug server. Use jhsdb jstack instead > > > > jcmd 69 Thread.print > > 69: > > com.sun.tools.attach.AttachNotSupportedException: Unable to open socket file > > /proc/69/root/tmp/.java_pid69: target process 69 doesn't respond within > > 10500ms or HotSpot VM not loaded > > at > > jdk.attach/sun.tools.attach.VirtualMachineImpl.<init>(VirtualMachineImpl. > > java:103) > > at > > jdk.attach/sun.tools.attach.AttachProviderImpl. > > attachVirtualMachine(AttachProviderImpl.java:58) > > at > > jdk.attach/com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java: > > 207) > > at jdk.jcmd/sun.tools.jcmd.JCmd.executeCommandForPid(JCmd.java:113) > > at jdk.jcmd/sun.tools.jcmd.JCmd.main(JCmd.java:97) > > > > Even kill -3 <pid> is not working. > > > > Thanks again for all the help! > > > > > (In reply to Madhuri Jain from comment #4) > > > > Hi, > > > > Thank you very much for your response. > > > > > > > > It's an HTTP based web test plan but we have not set any timeout > > > > explicitly > > > > (must be defaults if any). > > > > > > By default, we wait infinitely which can be a cause for hanging. > > > So please try setting in Advanced tab connect (500 is an acceptable value) > > > and read (30000) timeouts and see if it hangs. > > > > > > > For more details, the test plan is attached in > > > > the bug. > > > > > > > > The JMeter distributed setup is running on jre-headless docker image so > > > > it > > > > lacks jdk utilities. I'm facing two issues while getting thread dump: > > > > > > > > 1. The issue is occurring inconsistently and randomly. > > > > > > You can probably install a jdk instead and you'll have it; > > > > > > > > 2. While trying to run jmeter threaddump.sh, this only works on JMeter > > > > client (attached thread dump) but not on JMeter servers. Is there a way > > > > to > > > > run it and get thread dump on JMeter server? > > > > > > Install a JDK on your docker image > > > Connect to it using bash and run jstack from inside the image > > > > > > > > > > > Thanks! > > > > > > > > (In reply to Philippe Mouawad from comment #1) > > > > > Hello, > > > > > If it's an HTTP based load test, have you set connect and read > > > > > timeout on > > > > > HTTP Requests ? > > > > > > > > > > If it's another type of test, check that you don't have hanging > > > > > samplers. > > > > > > > > > > If you identify the hanging node, then run a thread dump using jstack > > > > > or > > > > > jmeter threaddump.sh and attach output here. > > > > > > > > > > Thanks -- You are receiving this mail because: You are the assignee for the bug.
