-
-
Notifications
You must be signed in to change notification settings - Fork 236
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
customPropertiesFile properties are not being sent to slave machines #383
Comments
So is the issue here that global properties are not being sent out to the slaves? If so it sounds like a JMeter bug at first glance. We supply a list of global properties to the JMeter command line using the -G flag, as part of your build you will see the following line in the console:
You should see something in there along the lines of |
PFB logs.
property File details
below is the log from slave machine
in the above logs, threads count, ramp up properties are not applied from property file on slave machine. |
That all looks to be working correctly, the global properties are being applied to the secondary as per:
Only global properties will be passed down to secondaries. |
Yes I get that. But I wanted to apply the properties from customProperty file to all the slaves. How can I do that ? |
JMeter doesn't support that as far as I'm aware, it only passes global properties through to the secondary. It sounds like what you really want this: #35 |
You can of course use the plugin to start up the secondary instances, then it will be configured in the same way as the master, the following IT POM may provide some guidance: https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/blob/master/src/it/remote-test/pom.xml |
I've tried the above pom xml. however it did not send the properties to slave machines. also noticed one more point with above pom.xml . It is trying to configure localhost as remote server automatically. Similar to this, is there any way to start the remote servers on slave machines ? |
It is not possible to configure the plugin to arbitrarily run commands upon another machine to start up a JMeter server instance. You would need to run your project on that other machine to start up a JMeter instance |
Version details
Jmeter version 5.3
Jmeter-Maven -Plugin version - 3.1.0
Java version 8
What should have happen
The plugin should copy all the properties to slave machine as well
What happened
The property file is applied only on master. it did not forwarded to slave
The text was updated successfully, but these errors were encountered: