https://bz.apache.org/bugzilla/show_bug.cgi?id=65000
--- Comment #5 from Philippe Mouawad <[email protected]> --- (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.
