CODEWITHSUNDEEP
httprequestjmeterload-testingperformance-testing
sam
sam

Reputation: 4684

jmeter hangs up and won't return

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

But on most of the cases jmeter hangs up and won' t return, even if I try to close the connection it just hangs up. and eventually I have to close the application.

Any idea how to check what is holding the requests and how to check the requests sent by jmeter and find the bottleneck.

Got the following message on closing the thread

Shutting down thread please be patient message

Upvotes: 4

Views: 10200

Answers (6)

Menelaos Kotsollaris
Menelaos Kotsollaris

Reputation: 5506

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

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

You can solve this by doing Remote Testing and have multiple clusters running, instead of one.

Upvotes: 0

Remy
Remy

Reputation: 540

I had the

one or more test threads won't exit

because of a firewall blocking some requests. So I had to leap in the firewalls timeout for all blocked request... then it returned.

Upvotes: 0

Mr. Programmer
Mr. Programmer

Reputation: 3103

I also encountered this problem before when I run my JMeter on my laptop(Core 2 Duo 1.5Ghz) it always hang-up in the middle of the processing. I tried to run on another pc which is more powerful than my laptop and its works now smoothly. Therefore, JMeter will run effectively if your pc or laptop has a better specs.

Note: It is also advisable to run your JMeter in non-gui mode. Example to run JMeter in Linux box:

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

Upvotes: 0

MetaCoder
MetaCoder

Reputation: 478

I've hit this several times over the past few years. In each of my cases (may not be in your's) the issue was with the Load Balance (F5) I was sending my traffic through. Basically a property called OneConnect was holding the connections in a time-wait state and never killing the connection.

Run a pack tool like wireshark and see what's happening with the requests.

Upvotes: 3

Akshay Saraswat
Akshay Saraswat

Reputation: 11

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

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

Upvotes: 1

UBIK LOAD PACK
UBIK LOAD PACK

Reputation: 34526

First check you script is ok with one user. Ensure you use assertions.

Then run you test following jmeter best practices:

  • no gui

  • no costly listeners

You should then be able to see in csv output the longest request and be able to fix your issue.

Upvotes: 0

Related Questions