CSV problem solved too. thanks Ivan for your insight in distribution load test
On Thu, 14 Mar 2019 at 16:53, Prateek Dua <prateek....@go-mmt.com> wrote: > Hi Ivan, > > We are able to do connectivity but on providing CSV , load is not getting > distributed to slaves. I have gone through below link but still CSV is not > getting picked for Master & Slave. > > > https://sqa.stackexchange.com/questions/14648/issue-with-reading-csv-file-when-doing-distributed-testing-in-jmeter > > The easiest way to resolve this issue is to place the *CSV* file on all > servers *(Master and Slaves)*inside the *Bin* directory of JMeter and *don't > specify any path for the CSV file* inside the your JMeter test plan i.e. > don't use C:\Data\Files\abc.csv in your test plan, *use only abc.csv* (and > place this file in Bin directory). Also, it will be good to keep the test > plan too in the Bin directory of the Master system JMeter. > > But if you want to use the relative path like C:\Data\abc.csv, then make > sure that this location exists on all the Slave systems and CSV file is > present there at this location on all Slave systems. This thing may not > work if your slave systems have different OS, like one slave is using > Windows and another is Linux, then you should go with the first method > which is the simplest and easiest one. > > On Thu, Mar 14, 2019 at 1:31 AM Ivan Rancati <ivan.ranc...@gmail.com> > wrote: > >> Two things you might have to check >> >> 1) keystore >> since JMeter 4.0 you have to either configure a keystore for RMI, or >> disable rmi over ssl >> (see https://jmeter.apache.org/usermanual/remote-test.html#setup_ssl) >> >> 2) Is the rmi port (default 1099) open? >> From the master, does telnet <ip of one of the slaves> 1099 work, or do >> you >> get a "connection refused"? >> From one of the slaves, does telnet <ip of the master> 1099 work? >> >> best regards, >> Ivan >> >> On Wed, Mar 13, 2019 at 8:02 PM Prateek Dua <prateek....@go-mmt.com> >> wrote: >> >> > Hi Guys, >> > >> > As per earlier discussion & suggestions on Distributed Load testing to >> > achieve Max concurrency, I've configured my jmeter set up on aws server >> per >> > this link >> > >> > >> https://www.blazemeter.com/blog/how-to-perform-distributed-testing-in-jmeter >> > >> > But still my master is unable to connect to slave machines . getting >> > *connection >> > time out error *always whenever Master tries to connect to Slave. >> > >> > >> > Configuring remote engine: 10.30.x.x (slave ip) >> > >> > ERROR org.apache.jmeter.engine.DistributedRunner - Failed to create >> engine >> > at 10.30.x.x ( Slave ip) >> > >> > java.rmi.ConnectException: Connection refused to host: 10.30.x. x ; >> nested >> > exception is: >> > >> > java.net.ConnectException: Connection timed out (Connection timed out) >> > >> > >> > Configuring remote engine: 10.30.x.x >> > Connection refused to host: 10.30.4.210; nested exception is: >> > java.net.ConnectException: Connection timed out (Connection timed out) >> > Failed to configure 10.30.x.x >> > >> > *Let me give a brief of what I have done* >> > >> > 1. Got 5 more aws slave instances & *all instances are replicas of >> Master >> > instance *having same Jmeter & Java & Jenkins version of Master >> instance . >> > >> > 2. All slave & master instances are on same subnet. >> > >> > 3. In jmeter.properties file of Master Server , added IPs of all the >> slave >> > systems against remote_hosts property. >> > >> > 4. Started jmeter.server file on all slave instances by running cmd >> > *./jmeter-server *& used another alternate cmd too *./jmeter-server >> > -Djava.rmi.server.hostname=10.30.x.x. ( Slave IP)* >> > >> > *Output on running both cmds -> *Created remote object: UnicastServerRef >> > [liveRef: >> > [endpoint:[10.30.x.x:37279](local),objID:[ae7eac4:169775d4503:-7fff, >> > 7214156034065384624]] >> > >> > 5. Passed param in non gui mode in script as -R slave 1, slavve 2 from >> > Master Server ./jmeter -n -t >> > >> > >> /var/lib/jenkins/workspace/apache-jmeter-4.0/extras/deployjmeter/throughput.jmx >> > -R 10.30.x.x >> > >> > 6 Although I'm starting Jmeter in non gui mode as shell script inside >> > Jenkins but on directly running via cmd line too -- I'm getting >> connection >> > Timeout error. >> > >> > *Can you guys let me know the mistake or steps I'm missing i.e.* >> > >> > -- Do I have to start jmeter-server on Master Server too ? >> > >> > -- Any port or network connecting issue among Master & Slave ? >> > >> > -- further changes to be done in any file of Master or Server ? >> > >> > -- Is it because Slaves are replicas of Master Instance having same >> jmeter >> > & jenkins version ( but differ in terms of IP ) >> > >> > -- >> > >> > >> > ::DISCLAIMER:: >> > >> > >> > >> > >> ---------------------------------------------------------------------------------------------------------------------------------------------------- >> > >> > >> > >> > >> > >> > This message is intended only for the use of the addressee and may >> > contain information that is privileged, confidential and exempt from >> > disclosure under applicable law. If the reader of this message is not >> the >> > intended recipient, or the employee or agent responsible for delivering >> > the >> > message to the intended recipient, you are hereby notified that any >> > dissemination, distribution or copying of this communication is strictly >> > prohibited. If you have received this e-mail in error, please notify us >> > immediately by return e-mail and delete this e-mail and all attachments >> > from your system. >> > >> > -- sent via device, pls ignore typos. -- ::DISCLAIMER:: ---------------------------------------------------------------------------------------------------------------------------------------------------- This message is intended only for the use of the addressee and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify us immediately by return e-mail and delete this e-mail and all attachments from your system.
