jMeter stucks after execute a test

1
votes

I'm developing a distributed test using jMeter with one slave machine and a simple test script (http request to home): 

./jmeter -n -t tests/TestPlan.jmx -r -l logs/log_test2.csv -X

But when I execute it, jMeter stucks at:

Waiting for possible Shutdown/StopTestNow/Heapdump message on port 4445

I googled and I've find that I can send a shutdown signal using shutdown script, but after execute it jMeter stucks at:

Command: Shutdown received from /127.0.0.1

This happens too if I execute stoptest.

What am I doing wrong?

2
javajmeterload-testing
did you tried also stoptest command? – user7294900
I'm trying all the commands, without good results – P. Rodoreda
Welcome to StackOverflow! Please have a look at the guides for asking questions, specifically how to create a Minimal, Complete, and Verifiable example – AesSedai101
Can you try CTRL+C when you see that message? – Pieter De Bie
I can, but nothing is storaged in my computer and I can't see the test's result. – P. Rodoreda

2 Answers

1
votes

I found that if I execute jMeter specifying rmi hostname, like:

./jmeter -n -t tests/TestPlan.jmx -r -l logs/log_test2.csv -Djava.rmi.server.hostname=192.168.150.59

It runs good.

0
votes

It usually indicates that JMeter either lacks hardware resources or it is not properly configured for conducting that high load.

  1. Make sure you're following JMeter Best Practices
  2. Make sure you're following recommendations from 9 Easy Solutions for a JMeter Load Test “Out of Memory” Failure guide
  3. Make sure you have monitoring of baseline OS and JVM health metrics on the host where JMeter load generator is running, it can be done using i.e. JMeter PerfMon Plugin and/or JVisualVM
  4. If you still experience issues with test graceful termination you can try adding another load generator host to see if it helps. Be aware that load generators are independent so if you define 100 threads under Thread Group - each JMeter slave will execute 100 threads. See Remote Testing user manual chapter for more details.
  5. Get used to check jmeter.log file, normally it contains enough troubleshooting information to get to the bottom of JMeter issues.