CODEWITHSUNDEEP
linuxamazon-web-servicesamazon-ec2jmeterdistributed-testing
janet.s
janet.s

Reputation: 11

JMeter-server freezes after starting test

I am doing jmeter distributed testing in AWS ec2 instance. My jmeter client machine(master) is in different AWS region on windows platform and jmeter server machine(slave) ) is in another region on linux platform. JMeter server is using public IP.

But when I remote start the jmeter server, it shows “starting the test on host xx.xx.xx.xx @…..” in linux terminal. After that nothing showing in the terminal and no results in jmeter client GUI. Even not hitting the application server(target server-hosted my own app). And it is taking more than 2 minutes to show that the test has started in linux terminal.

No errors showing in jmeter client GUI error log. Here is my GUI log..

   2016/03/16 05:03:59 INFO  - jmeter.engine.DistributedRunner: Configuring remote engine: xx.xx.xx.xx 
   2016/03/16 05:04:00 INFO  - jmeter.engine.DistributedRunner: Starting remote engines 
   2016/03/16 05:04:00 INFO  - jmeter.engine.DistributedRunner: Starting the test @ Wed Mar 16 05:04:00 UTC 2016 (1458104640482) 
   2016/03/16 05:04:00 INFO  - jmeter.engine.ClientJMeterEngine: running clientengine run method 
   2016/03/16 05:04:00 INFO  - jmeter.samplers.BatchSampleSender: Using batching (client settings) for this run. Thresholds: num=100, time=60000 
   2016/03/16 05:04:00 INFO  - jmeter.samplers.DataStrippingSampleSender: Using DataStrippingSampleSender for this run 
   2016/03/16 05:04:00 INFO  - jmeter.samplers.BatchSampleSender: Using batching (client settings) for this run. Thresholds: num=100, time=60000 
   2016/03/16 05:04:00 INFO  - jmeter.samplers.DataStrippingSampleSender: Using DataStrippingSampleSender for this run 
   2016/03/16 05:04:00 INFO  - jmeter.samplers.BatchSampleSender: Using batching (client settings) for this run. Thresholds: num=100, time=60000 
   2016/03/16 05:04:00 INFO  - jmeter.samplers.DataStrippingSampleSender: Using DataStrippingSampleSender for this run 
   2016/03/16 05:06:09 INFO  - jmeter.engine.ClientJMeterEngine: sent test to xx.xx.xx.xx basedir='.' 
   2016/03/16 05:06:09 INFO  - jmeter.engine.ClientJMeterEngine: Sending properties {} 
   2016/03/16 05:06:09 INFO  - jmeter.engine.ClientJMeterEngine: sent run command to xx.xx.xx.xx 
   2016/03/16 05:06:09 INFO  - jmeter.engine.DistributedRunner: Remote engines have been started

Please help to solve this....

Upvotes: 0

Views: 1728

Answers (1)

TestingWithArif
TestingWithArif

Reputation: 894

JMeter official distributed guide states that JMeter server and clients MUST be on same subnet. Have you checked if they share the same subnet addresses?

all the clients are on the same subnet.

the server is in the same subnet.

https://jmeter.apache.org/usermanual/jmeter_distributed_testing_step_by_step.pdf

I personally created my JMeter master/slave machines in same region (using same security group). Subnet addresses were same. I did not faced any issue in scripts execution. Please check on network addresses of JMeter machines and ensure that they share same subnet.

Upvotes: 0

Related Questions