[SOLVED] Why does my JMeter freeze at the end of execution in NOT GUI mode?

Why does my JMeter freeze at the end of execution in NOT GUI mode?

I am running performance tests of a createUser API in the NON GUI mode of JMeter. The configuration is a thread having 8000 users for 8 secs. The execution crashes at the end without displaying anything in the console or the logs, I need to stop the execution with a shutdown.

I can't find an explanation what is happening and how to identify the problem.

Console:

apache-jmeter-5.6.3\bin>jmeter -n -t "C:\script\Createusers.jmx"  -l "C:\Reports\Ngui8000.jlt"  -e -o "C:\Reports\htmlNGui8000sec"
WARN StatusConsoleListener The use of package scanning to locate plugins is deprecated and will be removed in a future release
WARN StatusConsoleListener The use of package scanning to locate plugins is deprecated and will be removed in a future release
WARN StatusConsoleListener The use of package scanning to locate plugins is deprecated and will be removed in a future release
WARN StatusConsoleListener The use of package scanning to locate plugins is deprecated and will be removed in a future release
Creating summariser <summary>
Created the tree successfully using C:\script\Createusers.jmx.jmx
Starting standalone test @ 2025 Jul 8 18:13:51 CEST (1751991231000)
Waiting for possible Shutdown/StopTestNow/HeapDump/ThreadDump message on port 4445
summary +      1 in 00:00:13 =    0.1/s Avg:  8617 Min:  8617 Max:  8617 Err:     0 (0.00%) Active: 6419 Started: 6419 Finished: 0
summary +   3536 in 00:00:26 =  136.2/s Avg: 22090 Min:  4350 Max: 38500 Err:  2406 (68.04%) Active: 4464 Started: 8000 Finished: 3536
summary =   3537 in 00:00:39 =   91.2/s Avg: 22086 Min:  4350 Max: 38500 Err:  2406 (68.02%)
summary +   2146 in 00:00:30 =   71.5/s Avg: 43382 Min: 23189 Max: 67476 Err:    96 (4.47%) Active: 2318 Started: 8000 Finished: 5682
summary =   5683 in 00:01:09 =   82.6/s Avg: 30128 Min:  4350 Max: 67476 Err:  2502 (44.03%)
summary +   1648 in 00:00:30 =   54.9/s Avg: 71639 Min: 52860 Max: 97227 Err:    21 (1.27%) Active: 670 Started: 8000 Finished: 7330
summary =   7331 in 00:01:39 =   74.2/s Avg: 39459 Min:  4350 Max: 97227 Err:  2523 (34.42%)
summary +    669 in 00:40:46 =    0.3/s Avg: 124192 Min: 83900 Max: 2537267 Err:   349 (52.17%) Active: 0 Started: 8000 Finished: 8000
summary =   8000 in 00:42:25 =    3.1/s Avg: 46545 Min:  4350 Max: 2537267 Err:  2872 (35.90%)
Tidying up ...    @ 2025 Jul 8 18:56:16 CEST (1751993776316)
... end of run

Solution

Your test doesn't last for 8 seconds as JMeter waits for response for each and every sampler and I can see response times up to 42 minutes. You might want to set up maximum response timeouts in HTTP Request Defaults
If you still experience the issue you might want to take a thread dump and see what thread (virtual user) is doing what and where exactly it got stuck
8000 virtual users might be too high amount for default JMeter settings, JMeter comes with limited JVM heap space and GC tuning, check out 9 Easy Solutions for a JMeter Load Test “Out of Memory” Failure article to learn how to get the most of your JMeter installation. It also might be the case you will need to consider switching to Distributed Testing