Jmeter hangs up and will not return

Question

I am running 340 concurrent users to load a test on the server using jmeter.

But in most cases, jmeter hangs and will not return even if I try to close the connection that it just hangs. and in the end I have to close the application.

Any idea how to check what holds requests, and how to check requests sent by jmeter and find a bottleneck.

Received the following thread shutdown message

Shutting down thread please be patient message 

Answer 1

I have come across this several times several times over the past few years. In each of my cases (it may not be in yours), the problem was related to the load balance (F5), with which I sent my traffic. In principle, the OneConnect property kept connections on hold and never killed a connection.

Run a batch tool like wirehark and see what happens with the queries.

Answer 2

Try distributed testing, 340 concurrent users is not a big deal, but you can try if it reduces your pain. Also take a look at the following link:

http://jmeter.apache.org/usermanual/best-practices.html#lean_mean

Answer 3

First check that you script is in order with a single user. Make sure you use assertions.

Then run the test following the best practices of jmeter:

• no gui

• no expensive listeners

Then you can see the longest request in csv and you can fix your problem.

Answer 4

I also ran into this problem before I ran my JMeter on my laptop (Core 2 Duo 1.5Ghz), which always freezes in the middle of processing. I tried to run on another PC, which is now more powerful than my laptop, and its work is now smooth. Therefore, JMeter will work efficiently if your computer or laptop has the best specifications.

Note. It is also recommended to run JMeter in non-gui mode. Example of running JMeter on Linux:

 $ ./jmeter -t test.jmx -n -l /Users/home/test.jtl 

Answer 5

I had

one or more test threads will not exit

due to a firewall blocking some requests. So I had to jump into the firewall timeout for all blocked requests ... then it came back.

Answer 6

You are probably getting this error because the JVM is not capable of starting so many threads. If you look at your terminal, you will see an exception that you will get:

Uncaught Exception java.lang.OutOfMemoryError: Unable to create new native thread. See the log file for details.

You can solve this problem by doing Remote Testing and enable multiple clusters instead of one.