Jmeter GUI mode not stopping execution when stop condition has been reached (a few threads cannot be stopped)
I am using Jmeter 5.2.1 with the "Classic" Thread group in order to simulate a stress scenario in which the load is continuously ramped-up to 400 threads over 2 hours. I added an AutoStop Listener which should stop the script execution when the average response Time is greater than 4000 for 20 seconds or the error rate is greater than 1% for 20 seconds.
Below is a screenshot of the Thread Group where you can also see the time shown in the top-right (well over 2 hours) which is still going at the time of writhing this (the timer is not stopping), and also the log where it's shown that the AutoStop Listener has triggered the stop condition and threads have started stopping and in the other screenshot you can see that the log writes many "Thread finished" statements, but I think the problem is that a few of the threads are hung somehow and jmeter cannot stop them.
Update: Adding another screenshot after pressing the "Stop" button from the jmeter gui. Note the time gap between the last log and the time I press the Stop button. There you can see that only after I press the button, only then I get log messages such as: Stopping: Thread Group 1-1 Interrupting: Thread Group 1-1 Stopping because end time detected by thread: Thread Group 1-1 And in the end: Notifying test listeners of end of test
Can someone please help me understand this behavior? Why isn't the execution stopping on its own?
When you launch JMeter it displays this message:
so you should not be using JMeter GUI for anything but test development and debugging, when it comes to test execution you should be running JMeter in command-line non-GUI mode like:
jmeter -n -t /path/to/your/testplan.jmx -l /path/to/results.jtl
when the test finishes you can generate HTML Reporting Dashboard to analyze the results
If you need to observe metrics in the real time you can use Backend Listener or Taurus framework
- Is there a good way to distinguish spurious wake up and Thread.interrupt()?
- std::lock_guard or std::scoped_lock?
- Synchronizing on String objects in Java
- Point Cloud Library (PCL) filtering timeout
- Managing multiple exclusive locks for a set of unique values
- Run external command in bg (other thread), capture output when available for rendering in TUI
- Do Java 21 virtual threads address the main reason to switch to reactive single-thread frameworks?
- Why did entering a lock on a UI thread trigger an OnPaint event?
- What's the difference between "static" and "dynamic" schedule in OpenMP?
- What is the best way to make a parent thread wait after initializing a child pthread until it receives some signal from the child?
- How to implement background polling in WinUI application in c#
- Java multithreading concept and join() method
- Detaching a thread versus calling pthread_exit() from main(), consequences for resources and memory in both scenarios
- Multiprocessing example giving AttributeError in Jupyter Notebook
- Peterson's Algorithm's behavior for various optimization flags
- ForkJoinPool.commonPool's threads are created new indefinitely instead of reused/closed when calling CompletableFuture methods of OpenFGA
- Is a function pointer variable always defined/legal for multithreading (thread-safe)(atomic) in C?
- Using multi-cores for increased parallel performance
- How to use a managed Tauri state variable inside a spawned tauri async runtime thread?
- Counter value is not decreasing while using multithreaded loop
- how to use handler on android concurrently?
- Using threading to load textures in Raylib is failing
- Problems implementing properly a Parallel.ForΕach loop and continue other work in the mean time
- Why is "kill" is not exiting a thread immediately?
- Synchronization of non-final field
- Can Virtual Threads improve querying a database in Java?
- Running code in main thread from another thread
- Understanding the volatile Modifier in the Context of x86 Architecture and the Java Memory Model (JMM)
- Is assigning a pointer in C program considered atomic on x86-64
- Removing items from bottom of ConcurrentStack<T> or equivalent functionality