13. Introduction to listeners¶
A listener is a component that shows the results of the samples. The results can be shown in a tree, tables, graphs or simply written to a log file. To view the contents of a response from any given sampler, add either of the Listeners "View @@ -464,7 +464,7 @@ e.g. a spreadsheet or text editor.
Copyright ©
1999 –
- 2016
+ 2017
, Apache Software Foundation
Apache, Apache JMeter, JMeter, the Apache
feather, and the Apache JMeter logo are
Modified: jmeter/trunk/docs/usermanual/properties_reference.html
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/usermanual/properties_reference.html?rev=1789801&r1=1789800&r2=1789801&view=diff
==============================================================================
--- jmeter/trunk/docs/usermanual/properties_reference.html (original)
+++ jmeter/trunk/docs/usermanual/properties_reference.html Sat Apr 1 14:01:02 2017
@@ -5,7 +5,7 @@
APACHE LOGO
-->
- 20 Introduction
- 20.1 Language
- 20.2 XML Parser
- 20.3 SSL configuration
- 20.4 Look and Feel configuration
- 20.5 Toolbar display
-
20.6 JMX Backup configuration
- 20.7 Remote hosts and RMI configuration
- 20.8 Include Controller
- 20.9 Logging Configuration
- 20.10 HTTP Java configuration
- 20.11 Commons and Apache HttpClient common properties
- 20.12 Kerberos properties
- 20.13 Sample logging levels for Commons HttpClient
- 20.14 Apache HttpClient logging examples
- 20.15 Apache HttpComponents HTTPClient configuration (HTTPClient4)
- 20.16 Apache HttpComponents Commons HTTPClient configuration (HTTPClient 3.1)
- 20.17 HTTP Cache Manager configuration
- 20.18 Results file configuration
- 20.19 Settings that affect SampleResults
- 20.20 Upgrade
- 20.21 JMeter Test Script recorder configuration
- 20.22 Test Script Recorder certificate configuration
- 20.23 JMeter Proxy configuration
- 20.24 HTML Parser configuration
- 20.25 Remote batching configuration
- 20.26 JDBC Request configuration
- 20.27 OS Process Sampler configuration
- 20.28 TCP Sampler configuration
- 20.29 Summariser - Generate Summary Results - configuration (mainly applies to non-GUI mode)
- 20.30 Aggregate Report and Aggregate Graph - configuration
- 20.31 BackendListener - configuration
- 20.32 BeanShell configuration
- 20.33 MailerModel configuration
- 20.34 CSVRead configuration
- 20.35 __time() function configuration
- 20.36 CSV DataSet configuration
- 20.37 LDAP Sampler configuration
- 20.38 Miscellaneous configuration
- 20.39 Classpath configuration
- 20.40 Reporting configuration
- 2
0.41 Additional property files to load
- 20.42 Thread Group Validation feature
- 20.43 Timer related feature
- 20 Introduction
- 20.1 Language
- 20.2 XML Parser
- 20.3 SSL configuration
- 20.4 Look and Feel configuration
- 20.5 Toolbar display< ul>
20 Introduction¶
This document describes JMeter properties. The properties present in jmeter.properties or reportgenerator.properties should be set in the user.properties file.
@@ -55,6 +55,9 @@ These properties are only taken into acc
JMeter no longer converts javax.xxx property entries in this file into System properties.
These must now be defined in the system.properties file or on the command-line.
The system.properties file gives more flexibility.
+ Parameters +
Attribute
Description
Required
https.sessioncontext.shared
By default, SSL session contexts are now created per-thread, rather than being shared.
The old behaviour can be enabled by setting this property to true. Defaults to: false @@ -72,9 +75,6 @@ The system.properties
The old behaviour can be enabled by setting this property to true. Defaults to: false @@ -72,9 +75,6 @@ The system.properties
No
- Parameters -
Attribute
Description
Required
https.socket.protocols
List of protocols to enable. You may have to select only a subset if you find issues with target server.
This is needed when server does not support Socket version negotiation, this can lead to errors like: @@ -130,7 +130,7 @@ The system.properties
This is needed when server does not support Socket version negotiation, this can lead to errors like: @@ -130,7 +130,7 @@ The system.properties
Mac apparently looks better with the System LAF set through
jmeter.laf.mac=System- Failing that, the JMeter default laf can be defined through: + Failing that, the JMeter default LAF can be defined through:
jmeter.laf=SystemIf none of the above jmeter.laf properties are defined, JMeter uses the CrossPlatform LAF. This is because the CrossPlatform LAF generally looks better than the System LAF. @@ -154,8 +154,13 @@ The system.properties No
jmeter.loggerpanel.maxlength
- Max characters kept in LoggerPanel, 0 means no limit.
- Defaults to: 80000
- Defaults to: 80000
+ Max lines kept in LoggerPanel, 0 means no limit.
+ Defaults to: 1000
+ Defaults to: 1000
+ No
+
jmeter.gui.refresh_period
+ Interval period in ms to process the events of the listeners.
+ Defaults to: 500
+ Defaults to: 500
No
On the server(s): -
-
-
- set server_port=1234
- start rmiregistry with port 1234
-
+
- set server_port=1234 +
- start rmiregistry with port 1234 +
SET SERVER_PORT=1234 JMETER-SERVEROn Unix:
SERVER_PORT=1234 jmeter-server- On the windows client: + On the Windows client:
set remote_hosts=server:1234- On the unix client: + On the Unix client:
export remote_hosts=server:1234Defaults to: 1099
@@ -372,7 +377,7 @@ JMETER-SERVER
No
server.rmi.create
- From JMeter version 2.3.1, the jmeter server creates the RMI registry as part of the server process.
+ From JMeter version 2.3.1, the JMeter server creates the RMI registry as part of the server process.
Set this property to false, to stop the server creating the RMI registry.
Defaults to: true
+ From JMeter version 2.3.1, the JMeter server creates the RMI registry as part of the server process.
Set this property to false, to stop the server creating the RMI registry.
Defaults to: true
@@ -396,95 +401,7 @@ JMETER-SERVER
No
20.9 Logging Configuration¶
-
- JMeter uses Avalon (Excalibur) LogKit.
- The Logging Format is described here
- Default format: -
- - Combined log file (for jmeter and jorphan) -
- - 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 is specified, it will be applied to the current logging - hierarchy when that has been created. -
-- 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. -
Thread name is not included by default, as it requires extra processing.
-
- 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 -
-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 is specified, it will be applied to the current logging - hierarchy when that has been created. -
log_config=logkit.xml-
20.10 HTTP Java configuration¶
+20.9 HTTP Java configuration¶
Parameters
Attribute
Description
Required
20.11 Commons and Apache HttpClient common properties¶
+20.10 Apache HttpClient common properties¶
Parameters
Attribute
Description
Required
httpclient.timeout
Set the socket timeout (or use the parameter http.socket.timeout) for
- AJP Sampler and HttpClient3 implementation.
-
Value is in milliseconds, 0 means no timeout.
Defaults to: 0
-
Note for HttpClient3 implementation it is better to use GUI to set timeout or
- use http.socket.timeout in httpclient.parameters.
+ AJP Sampler.Value is in milliseconds, 0 means no timeout.
Defaults to: 0
@@ -541,7 +456,7 @@ log_file.jmeter=jmeter.log
No
20.12 Kerberos properties¶
+20.11 Kerberos properties¶
Parameters
Attribute
Description
Required