This document describes JMeter properties. The properties present in jmeter.properties or reportgenerator.properties should be set in the user.properties file. These properties are only taken into account after restarting JMeter as they are usually resolved when the class is loaded.

JMeter uses Avalon (Excalibur) LogKit The Logging Format is described here Default format:

log_format=%{time:yyyy/MM/dd HH:mm:ss} %5.5{priority} - %{category}: %{message} %{throwable}

\n is automatically added to the end of the string Predefined formats in the JMeter LoggingManager:

#log_format_type=default
#log_format_type=thread_prefix
#log_format_type=thread_suffix

default is as above. thread_prefix adds the thread name as a prefix to the category. thread_suffix adds the thread name as a suffix to the category To change the logging format, define either log_format_type or log_format If both are defined, the type takes precedence. Note that these properties cannot be defined using the -J or -D JMeter command-line flags, as the format will have already been determined by then However, they can be defined as JVM properties Logging levels for the logging categories in JMeter. Correct values are:

• FATAL_ERROR
• ERROR
• WARN
• INFO
• DEBUG

To set the log level for a package or individual class, use:

log_level.[package_name].[classname]=[PRIORITY_LEVEL]

But omit org.apache from the package name. The classname is optional. Further examples below.

log_level.jmeter=INFO
log_level.jmeter.junit=DEBUG
log_level.jmeter.control=DEBUG
log_level.jmeter.testbeans=DEBUG
log_level.jmeter.engine=DEBUG
log_level.jmeter.threads=DEBUG
log_level.jmeter.gui=WARN
log_level.jmeter.testelement=DEBUG
log_level.jmeter.util=WARN
log_level.jmeter.protocol.http=DEBUG
# For CookieManager, AuthManager etc:
log_level.jmeter.protocol.http.control=DEBUG
log_level.jmeter.protocol.ftp=WARN
log_level.jmeter.protocol.jdbc=DEBUG
log_level.jmeter.protocol.java=WARN
log_level.jmeter.testelements.property=DEBUG
log_level.jorphan=INFO

# You can specify a different log file for different categories via:

log_file.[category]=[filename]

category is equivalent to the package/class names described above Combined log file (for jmeter and jorphan)

log_file=jmeter.log

To redirect logging to standard output, try the following (it will probably report an error, but output will be to stdout):

log_file=

Or define separate logs if required:

log_file.jorphan=jorphan.log
log_file.jmeter=jmeter.log

If the filename contains paired single-quotes, then the name is processed as a SimpleDateFormat format applied to the current date, for example:

log_file='jmeter_'yyyyMMddHHmmss'.tmp'

When JMeter starts, it sets the system property: org.apache.commons.logging.Log to org.apache.commons.logging.impl.LogKitLogger if not already set. This causes Apache and Commons HttpClient to use the same logging as JMeter Excalibur logging provides the facility to configure logging using configuration files written in XML. This allows for such features as log file rotation which are not supported directly by JMeter. If such a file specified, it will be applied to the current logging hierarchy when that has been created.

log_config=logkit.xml

Commons HttpClient Logging information can be found at Logging Note that full category names are used, i.e. must include the org.apache. Info level produces no output. Set debug level:

log_level.org.apache.commons.httpclient=debug

Might be useful:

log_level.org.apache.commons.httpclient.Authenticator=trace

Show headers only

log_level.httpclient.wire.header=debug

Full wire debug produces a lot of output; consider using separate file:

log_level.httpclient.wire=debug
log_file.httpclient=httpclient.log

Enable header wire + context logging - Best for Debugging

log_level.org.apache.http=DEBUG
log_level.org.apache.http.wire=ERROR

Enable full wire + context logging

log_level.org.apache.http=DEBUG

Enable context logging for connection management

log_level.org.apache.http.impl.conn=DEBUG

Enable context logging for connection management / request execution

log_level.org.apache.http.impl.conn=DEBUG
log_level.org.apache.http.impl.client=DEBUG
log_level.org.apache.http.client=DEBUG

Validation is the name of the feature used to rapidly validate a Thread Group runs fine