apache / apache/jmeter

JMeter test not stopping after duration ends in distribution mode

Open
#5,455 11 comments 0 reactions 0 assignees View on GitHub
need info os: Linux P2
Dominant language
Java
Stars
9.5k
Forks
2.3k
Avg merge
1d 22h
Merged PRs (30d)
5

Description

**Madhuri Jain** ([Bug 65000](https://bz.apache.org/bugzilla//show_bug.cgi?id=65000&redirect=false)):
I'm running a very simple JMeter test with Basic Thread Group and HTTP Sampler. The duration set for execution is 10 min (600 sec).

The test ran and stopped itself (after 10 min) successfully on my local both in JMeter GUI as well as CLI mode.

However, when I run the same test in distributed mode, the test does not stop itself and gets hanged. I've been observing this issue mostly with more thread count 200 or more worker count (~10).

Some of the JMeter properties I have overridden:

"server.rmi.ssl.disable": "true",
"jmeterengine.nongui.maxport": JMETER_EXEC_PORT,
"jmeterengine.nongui.port": JMETER_EXEC_PORT,
"client.tries": str(3),
"client.retries_delay": str(5000),
"client.rmi.localport": CLIENT_RMI_LOCALPORT,
"server.rmi.localport": SERVER_RMI_LOCALPORT,
"server_port": SERVER_PORT,
"server.exitaftertest": "true",
"jmeterengine.stopfail.system.exit": "true",
"jmeterengine.remote.system.exit": "true",
"jmeterengine.force.system.exit": "true",
"jmeter.save.saveservice.output_format": "csv",
"jmeter.save.saveservice.autoflush": "true",
"beanshell.server.file": "./extras/startup.bsh",
"jmeter.save.saveservice.connect_time": "true",
"jpgc.repo.sendstats": "false",
Here're the JMeter CLI commands I'm using for JMeter client and server respectively:

// JMeter Client
jmeter.sh -n -f -t {testPlan} -j jmeter.log -l report.csv -LINFO -Lorg.apache.http=DEBUG -Lorg.apache.http.wire=ERROR -Ljmeter.engine=DEBUG -X -R {serverIPs}

// JMeter Server
jmeter.sh -s -Jbeanshell.server.port={beanshellServerPort}

1. Any help pointers to make sure the test ends after the specified duration?
2. Can this be controlled/enforced by any JMeter setting/property?
3. Is it something related to Basic thread group v/s thread group plugins like Concurrency/Ultimate thread group?

Example test run:

I tried to run this test plan with 10 workers out of which 6 were successfully finished while 4 of them hanged. Please find attached the logs and test plan.

Also, why does the Summariser show Active + Finished threads more than Started?

Trail of Worker pod logs that is stuck:

2020-12-16 08:19:48,933 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: 10.244.11.4-Thread Group 1-86
2020-12-16 08:19:48,933 INFO o.a.j.t.JMeterThread: Thread finished: 10.244.11.4-Thread Group 1-86
2020-12-16 08:25:22,926 INFO o.a.j.e.RemoteJMeterEngineImpl: Shutting test ...
2020-12-16 08:25:22,927 INFO o.a.j.e.RemoteJMeterEngineImpl: ... stopped
2020-12-16 08:25:22,928 INFO o.a.j.t.JMeterThread: Stopping: 10.244.11.4-Thread Group 1-78
2020-12-16 08:25:22,928 INFO o.a.j.t.JMeterThread: Stopping: 10.244.11.4-Thread Group 1-190

Created attachment [jmeter_stuck_execution.zip](https://apache.github.io/jmeter-bugzilla-attachments/00/65000/37623/jmeter_stuck_execution.zip): test plan

Severity: normal
OS: Linux

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.