JMeter provides two ways to override Java, JMeter, and logging properties. One way is to directly edit jmeter.properties, which resides in the JMETER_HOME/bin folder. I suggest that you take a peek into this file and see the vast number of properties you can override. This is one of the things that makes JMeter so powerful and flexible. On most occasions, you will not need to override the defaults, as they have sensible default values.
The other way to override these values is directly from the command line when starting JMeter.
The options available to you include the following ones:
- Defining a Java system property value:
-D<property name>=<value>
- Defining a local JMeter property:
-J<property name>=<value>
- Defining a JMeter property to be sent to all remote servers:
-G<property name>=<value>
- Defining a file containing JMeter properties to be sent to all remote servers:
-G<property file>
- Overriding a logging setting, setting a category to a given priority level:
-L<category>=<priority>
./jmeter.sh -Duser.dir=/home/bobbyflare/jmeter_stuff
-Jremote_hosts=127.0.0.1 -Ljmeter.engine=DEBUG
Since command-line options are processed after the logging system has been set up, any attempt to use the -J flag to update the log_level or log_file properties will have no effect.