On Wed, Nov 18, 2015 at 9:28 AM, Meenakshi Sharma <[email protected]> wrote:
> Hi, > > I just started working with Jmeter. > > In the longer run, I would like to setup Jmeter Distributed tests on EC2 to > generate huge load. This is how far I have reached: > > 1. Created and Launched EC2 instances (3 right now so that I can use 1 > master and 2 slaves) with following security settings since 1099 is the > Java RMI Registry port... > Custom TCP RuleTCP10990.0.0.0/02. Installed jmeter: 2.8.20130705 and > java: 1.7.0_80 on all 3 instances > That's a really old version of JMeter. The latest release is 2.13. I'd recommend updating to the latest version to ensure you aren't hitting some obscure bug that's been fixed since 2.8. > 3. Before I begin implementing Master-Slave configuration, I am trying to > run a small test from just 1 EC2 instance to check if it is able to send/ > receive data to/ from the web-site (not on AWS). > > The test is a simple GET request for the home page. > > 4. I run following command: > jmeter -n -t ../testplans/HTTP\ Request.jmx > Output: > Created the tree successfully using ../testplans/HTTP Request.jmx > Starting the test @ Tue Nov 17 21:31:46 UTC 2015 (1447795906236) > Waiting for possible shutdown message on port 4445 > > 5. Even from UI there is no result or summary > > Could somebody help with the set-up next step? > I think I am missing some basic configuration. Let me know if there are any > questions. > Can you log into one of the EC2 instances and hit the site without going through JMeter (e.g. if it's a Windows VM, try hitting the site in Internet Explorer from the EC2 instance. If it's Linux, try `curl <your website url>`)? If that works, then the issue is somewhere within JMeter or the test plan. If it doesn't work (and especially if you aren't able to ping the site from the EC2 instance), then the problem is outside of JMeter and you probably need to talk to your network team about adding some firewall burns. > Thank you. > Meena >
