Modified: jmeter/trunk/docs/changes.html URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/changes.html?rev=1789801&r1=1789800&r2=1789801&view=diff ============================================================================== --- jmeter/trunk/docs/changes.html (original) +++ jmeter/trunk/docs/changes.html Sat Apr 1 14:01:02 2017 @@ -5,7 +5,7 @@ APACHE LOGO -->

Changes

+ -->
< div class="main" id="content">

Changes

This page details the changes made in the current version only. @@ -16,7 +16,7 @@ Earlier changes are detailed in the Version 3.1 +

Version 3.2

Summary

@@ -33,541 +33,559 @@ Summary

New and Noteworthy

-

Improve Report/Dashboard

-

-The Dashboard has been improved with 3 new graphs and 1 summary table: -

-
    -
  • Connect Time over Time graph :
    • -
  • Response Time Percentiles Over Time (successful responses) graph :
    • -
  • Response Time Overview graph :
    • -
  • Top 5 errors by Sampler table :
    • -
  • More details on errors in Errors table
    • -
  • Average response time added to Statistics table :
    • -
  • Active Threads table now stacks threads :
    • -
-

New Metrics

-

-A new sent_bytes metric has been introduced which reports the bytes sent to server.
-Another metric connect_time has been enabled by default in this version -

-

Handling Big responses

-

-JMeter is now able to handle in terms of metrics responses bigger than 2GB, limit has been increased to 9223372 TB.
-To handle such big responses, it can also now truncate part of the response to avoid overflooding memory. See httpsampler.max_bytes_to_store_per_request property. -

-

New __groovy function

-

-Introduce a new function __groovy that enables Groovy functions. This can be handy, as JavaScript can be quite slow (same for BeanShell), when used in highly concurrent test plans. -

-

Use Groovy as default for JSR-223 elements

+

IMPORTANT CHANGES

-Groovy is now set as the default language for JSR-223 elements. If you want to use another of the supported language, you have to make an explicit choice. +JMeter now requires Java 8. Ensure you use the most up to date version.

-
By default Cache compiled script if available is not checked by default although we advise you to check it and ensure you don't use ${varName} syntax to access JMeter variables but vars.get("varName") instead.
- -

Formatted HTML source view in Results Tree View

-The HTML source code in the Results Tree View can now be viewed formatted. This is extremely useful, if the code of the webpage has been stripped of all superfluous whitespace. +JMeter logging has been migrated to SLF4J and Log4j 2. +This affects configuration and 3rd party plugins, see below "Logging changes".

-
New formatted HTML source view
New formatted HTML source view
- -

Ability to update all timers in Test plan with a new property

-

-A new property timer.factor=1.0f has been introduced which allows you to multiply pause times computed by Gaussian, Uniform and Poisson Timers by it. -This allows you to update Think Times from one place and let you gain productivity. -

-

Core improvements

    -
  • Various GUI and UX fixes
    • -
  • Memory usage improvements
    • -
  • JDBC Request is now able to return Blob/Clob and computes latency and connect time
    • -
  • CSS Parsing introduced in 3.0 has been optimized by introduction of a parsing cache
    • -
  • HTTP Request is now able to handle body in GET request, this is useful for Elastic Search requests for example.
    • +
  • JMeter now provides a new BackendListener implementation that interfaces InfluxDB. +
    +This implementation sends data using Asynchronous HTTP calls to InfluxDB through its HTTP API +and give you the following graphs with annotations: +
    +
    • +
  • DNS Cache Manager now has a table to allow static host resolution. +
    +
    • +
  • JMS Publisher and Subscriber now allow reconnection on error with pause. +
    +
    +
    • +
  • Variables in JMS Publisher are now supported for all types of messages. Add the encoding type of the file to parse its content
    • +
    +
  • XPath Extractor now allows extraction randomly, by index or for all matches. +
    +
    • +
  • Response Assertion now allows to work on Request Header, provides a "OR" combination and has a better cell renderer +
    +
    • +
  • JMeter now uses Oracle Nashorn Javascript engine instead of Rhino. This provides a faster execution of Javascript.
    • +
  • HTTP HC4 Implementation now provides preemptive Basic Auth enabled by default
    • +
  • Embedded resources download in CSS has been improved to avoid useless repetitive parsing to find the resources
    • +
  • An important work on code quality and code coverage with tests has been done since Sonar has been setup on the project. +You can see Sonar report here. +
-

Documentation improvements

+

UX improvements

    -
  • Documentation review and improvements for easier startup
    • -
  • New properties reference documentation section
    • +
  • When running a Test, GUI is now more responsive and less impacting on memory usage thanks to a limitation on the number of Sample Results +listeners hold and a rework of the way GUI is updated
    • +
  • HTTP Request GUI has been simplified and provides more place for parameters and body. +
    +
    • +
  • HTTP(S) Test Script Recorder has been simplified and clarified. +
    +
    +
    • +
  • A replace feature has been added to Search feature to allow replacement in some elements. +
    +
    • +
  • View Results Tree now provides a more up to date Browser renderer which requires JavaFX.
    • +
  • You can now add through a contextual menu think times, this will add think times between samplers and Transaction Controllers + of selected node. +
    +
    • +
  • You can now apply a naming policy to children of a Transaction Controller. A default policy exists but you can implement your own + through org.apache.jmeter.gui.action.TreeNodeNamingPolicy + and configuring property naming_policy.impl +
    +
    • +
  • Sorting per column has been added to View Results in Table, Summary Report, Aggregate Report and Aggregate Graph elements. +
    +
+

Report/Dashboard improvements

+
    +
  • +Statistics have been reorganized to clarify report: +
    +
    • +
  • +It is now possible to customize APDEX thresholds per transaction based on regular expression or sample name. +The below example will apply different thresholds for samples sample(\\d+), sampleA and scenarioB +than default ones (500 and 1500 for satisfied and tolerated thresholds) declared: +
    +jmeter.reportgenerator.apdex_satisfied_threshold=500
+jmeter.reportgenerator.apdex_tolerated_threshold=1500
+jmeter.reportgenerator.apdex_per_transaction=sample(\\d+):1000|2000;\
+    sampleA:3000|4000;\
+    scenarioB:5000|6000
+
    +
    • +
- +

Documentation improvements

+
    +
  • PDF Documentations have been migrated and updated to HTML user manual
    • +

Incompatible changes

    -
  • A cache for CSS Parsing of URLs has been introduced in this version, it is enabled by default. It is controlled by property css.parser.cache.size. It can be disabled by setting its value to 0. See - Bug - 59885
    • -
  • ThroughputController defaults have changed. Now defaults are Percent Executions which is global and no more per user. See - Bug - 60023
    • -
  • Since version 3.1, HTML report ignores empty Transaction Controller (possibly generated by If Controller or Throughput Controller) when computing metrics. This provides more accurate metrics
    • -
  • Since version 3.1, Summariser ignores SampleResults generated by Transaction Controller when computing the live statistics, see - Bug - 60109
    • -
  • Since version 3.1, when using Stripped modes (by default StrippedBatch is used), response will be stripped also for failing SampleResults, you can revert this to previous behaviour by setting sample_sender_strip_also_on_error=false in user.properties, see +
  • JMeter requires now at least a Java 8 version to run.
    • +
  • JMeter logging has been migrated to SLF4J and Log4j 2, this involves changes in the way configuration is done. JMeter now relies on standard + Log4j 2 configuration in file log4j2.xml + See Logging changes section below for further details. +
    • +
  • The following jars have been removed after migration from LogKit to SLF4J (see Bug - 60137
    • -
  • Since version 3.1, jmeter.save.saveservice.connect_time property value is true, meaning CSV file for results will contain an additional column containing connection time, see + 60589): +
      +
    • ApacheJMeter_slf4j_logkit.jar
      • +
    • avalon-framework-4.1.4.jar
      • +
    • avalon-framework-4.1.4.jar
      • +
    • commons-logging-1.2.jar
      • +
    • excalibur-logger-1.1.jar
      • +
    • logkit-2.0.jar
      • +
    +
    • +
  • The commons-httpclient-3.1.jar has been removed after drop of HC3.1 support(see Bug - 60106
    • -
  • Since version 3.1, Random Timer subclasses (Gaussian Random Timer, Uniform Random Timer and Poisson Random Timer) implement interface org.apache.jmeter.timers.ModifiableTimer
    • -
  • Since version 3.1, if you don't select any language in JSR223 Test Elements, Apache Groovy language will be used. See + 60727)
    • +
  • JMeter now sets through -Djava.security.egd=file:/dev/urandom the algorithm for secure random
    • +
  • Process Sampler now returns error code 500 when an error occurs. It previously returned an empty value.
    • +
  • In org.apache.jmeter.protocol.http.sampler.HTTPHCAbstractImpl two protected static fields (localhost and nonProxyHostSuffixSize) have been renamed to (LOCALHOST and NON_PROXY_HOST_SUFFIX_SIZE) + to follow static fields naming convention
    • +
  • JMeter now uses by default Oracle Nashorn engine instead of Mozilla Rhino for better performances. This should not have an impact unless + you use some advanced features. You can revert back to Rhino by settings property javascript.use_rhino=true. + You can read this migration guide for more details on Nashorn. See Bug - 59945
    • -
  • Since version 3.1, CSV DataSet now trims variable names to avoid issues due to spaces between variables names when configuring CSV DataSet. This should not have any impact for you unless you use space at the begining or end of your variable names. See + 60672
    • +
  • Bug - 60221
    • -
  • Since version 3.1, HTTP Request is able when using HttpClient4 (default) implementation to handle responses bigger than 2147483647 Bytes, that is 2GB. To allow this two properties have been introduced: -
      -
    • httpsampler.max_bytes_to_store_per_request (defaults to 10MB) will control what is held in memory. By default JMeter will only keep in memory the first 10MB of a response. If you have responses larger than this value and use assertions that are after the first 10MB, then you must increase this value
      • -
    • httpsampler.max_buffer_size will control the buffer used to read the data. Previously JMeter used a buffer equal to Content-Length header which could lead to failures and make JMeter less resistant to faulty applications, but note this may impact response times and give slightly different results - than previous versions if your application returned a Content-Length header higher than current default value (65KB)
      • -
    - See + 60729 + - + The Random Variable Config Element now allows minimum==maximum. Previous versions logged an error when minimum==maximum and did not set the configured variable.
    • +
  • Bug - 53039
    • + 60730 + - + The JSON PostProcessor now sets the _ALL variable (assuming Compute concatenation var was checked) + even if the JSON path matches only once. Previous versions did not set the _ALL variable in this case.
-

Deprecated and removed elements or functions

-

These elements do not appear anymore in the menu, if you need them modify not_in_menu property. The JMeter team advises not to use them anymore and migrate to their replacement.

+

Removed elements or functions

    -
  • +
  • SOAP/XML-RPC Request has been removed as part of Bug - 60222 - - - Remove deprecated elements Distribution Graph, Spline Visualizer
    • -
  • - Bug - 60224 - - - Deprecate Monitor Results listener. It will be dropped in next version.
    • -
  • + 60727. Use HTTP Request element as a replacement. + See Building a WebService Test Plan
    • +
  • Bug - 60323 + 60423 - - Deprecate BSF Elements (Use JSR223 Elements instead). They will probably be dropped in N+2 version. The following elements are deprecated: - + Drop Monitor Results listener
    • +
  • Drop deprecated class org.apache.jmeter.protocol.system.NativeCommand
    • +
  • Drop deprecated class org.apache.jmeter.protocol.http.config.gui.MultipartUrlConfigGui
    • +
  • Drop deprecated class org.apache.jmeter.testelement.TestListener
    • +
  • Drop deprecated class org.apache.jmeter.reporters.FileReporter
    • +
  • Drop deprecated class org.apache.jmeter.protocol.http.modifier.UserSequence
    • +
  • Drop deprecated class org.apache.jmeter.protocol.http.parser.HTMLParseError
    • +
  • Drop unused methods org.apache.jmeter.protocol.http.control.HeaderManager#getSOAPHeader + and org.apache.jmeter.protocol.http.control.HeaderManager#setSOAPHeader(Object)
    • -
  • - Bug - 60225 - - - Drop deprecated __jexl function, jexl support in BSF and dependency on commons-jexl-1.1.jar. This function can be easily replaced with __jexl3 function
    • -
  • - Bug - 60268 - - - Drop org.apache.jmeter.gui.action.Analyze and deprecate org.apache.jmeter.reporters.FileReporter (will be removed in next version)
    • +
  • org.apache.jmeter.protocol.http.util.Base64Encode has been deprecated, you can use java.util.Base64 as a replacement
+

Logging changes

+

+ JMeter logging has been migrated to SLF4J and Log4j 2. + This affects logging configuration and 3rd party plugins (if they use JMeter logging). + The following sections describe what changes need to be made. +

+ +

Setting the logging level and log file

+

+ The default logging level can be changed on the command-line using the -L parameter. + Likewise the -l parameter can be used to change the name of the log file. + However the log_level properties no longer work. +

+

+ The default logging levels and file name are defined in the log4j2.xml configuration file + in the launch directory (usually JMETER_HOME/bin) +

+

+

If you need to change the level programmatically from Groovy code or Beanshell, you need to do the following: + 
+    import org.apache.logging.log4j.core.config.Configurator;
+    ⋮
+    final String loggerName = te.getClass().getName(); // te being a JMeter class
+    Configurator.setAllLevels(loggerName, Level.DEBUG); 
+
+
+

+ +

Changes to 3rd party plugin logging

+

+

3rd party plugins should migrate their logging code from logkit to slf4j. This is fairly easy and can be done by replacing: + 
+        import org.apache.jorphan.logging.LoggingManager;
+        import org.apache.log.Logger;
+        ⋮
+        private static final Logger log = LoggingManager.getLoggerForClass();
+
+ By: + 
+        import org.slf4j.Logger;
+        import org.slf4j.LoggerFactory;
+        ⋮
+        private static final Logger log = LoggerFactory.getLogger(YourClassName.class);
+
+
+

Improvements

HTTP Samplers and Test Script Recorder

Other samplers

Controllers

    -
  • - Bug - 59351 - - - Improve log/error/message for IncludeController. Partly contributed by Antonio Gomes Rodrigues (ra0077 at gmail.com)
    • -
  • - Bug - 60023 - - - ThroughputController : Make "Percent Executions" and global the default values. Contributed by Ubik Load Pack (support at ubikloadpack.com)
    • -
  • - Bug - 60082 - - - Validation mode : Be able to force Throughput Controller to run as if it was set to 100%
    • -
  • - Bug - 59349 - - - Trim spaces in input filename in IncludeController.
    • -
  • +
  • Bug - 60081 + 60672 - - Interleave Controller : Add an option to alternate across threads
    • + JavaScript function / IfController : use Nashorn engine by default

Listeners

- -

Timers, Assertions, Config, Pre- & Post-Processors

- + +

Timers, Assertions, Config, Pre- & Post-Processors

+

Functions

    -
  • - Bug - 59963 - - - New function __RandomFromMultipleVars: Ability to compute a random value from values of one or more variables. Contributed by Ubik Load Pack (support at ubikloadpack.com)
    • -
  • - Bug - 59991 - - - New function __groovy to evaluate Groovy Script. Contributed by Ubik Load Pack (support at ubikloadpack.com)

I18N

Report / Dashboard

+ +

General

+ -

General

-

Non-functional changes

@@ -576,213 +594,247 @@ This allows you to update Think Times fr

HTTP Samplers and Test Script Recorder

- -

Other Samplers

- - -

Controllers

- - -

Listeners

- - -

Timers, Assertions, Config, Pre- & Post-Processors

- -

Functions

+

Other Samplers

    +
  • + Bug + 603982 + - + Guard Exception handler of the JDBCSampler against null messages
    • +
  • + Bug + 55652 + - + JavaSampler silently resets classname if class can not be found
-

I18N

+

Controllers

-

General

+

Listeners

+ +

Timers, Assertions, Config, Pre- & Post-Processors

+ + +

Functions

+ + +

I18N

+
    +
+ +

Report / Dashboard

+ + +

General

+ @@ -791,24 +843,36 @@ This allows you to update Think Times fr

We thank all contributors mentioned in bug and improvement sections above:

    -
  • Felix Draxler (felix.draxler at sap.com)
    • -
  • Antonio Gomes Rodrigues (ra0077 at gmail.com)
    • -
  • Graham Russell (graham at ham1.co.uk)
    • -
  • Teemu Vesala (teemu.vesala at qentinel.com)
    • -
  • Asier Lostalé (asier.lostale at openbravo.com)
    • -
  • Thomas Peyrard (thomas.peyrard at murex.com)
    • -
  • Benoit Wiart (b.wiart at ubik-ingenierie.com)
    • +
  • Jerome Loisel (loisel.jerome at gmail.com)
    • +
  • Liu XP (liu_xp2003 at sina.com)
    • +
  • Qi Chen (qi.chensh at ele.me)
    • +
  • (gavin at 16degrees.com.au)
    • +
  • Thomas Schapitz (ts-nospam12 at online.de)
    • +
  • Murdecai777 (https://github.com/Murdecai777)
    • +
  • Logan Mauzaize (logan.mauzaize at gmail.com)
  • Maxime Chassagneux (maxime.chassagneux at gmail.com)
    • +
  • 忻隆 (298015902 at qq.com)
  • Ubik Load Pack
    • -
  • Tamas Szabadi (tamas.szabadi at rightside.co)
    • -
  • Roberto Braga (roberto.braga at soziale.it)
    • -
  • jarek102 at gmail.com
    • -
  • Wyatt Epp (wyatt.epp at gmail.com)
    • -
  • Thomas Schapitz (ts-nospam12 at online.de)
    • +
  • Graham Russell (graham at ham1.co.uk)
    • +
  • Sanduni Kanishka (https://github.com/SanduniKanishka)
    • +
  • Andrew Burton (andrewburtonatwh at gmail.com)
    • +
  • Woonsan Ko (woonsan at apache.org)
    • +
  • Bartosz Siewniak (barteksiewniak at gmail.com)
    • +
  • Kimono (kimono.outfit.am at gmail.com)
    • +
  • Michael Osipov (michaelo at apache.org)
    • +
  • Stephane Leplus (s.leplus at ubik-ingenierie.com)

We also thank bug reporters who helped us improve JMeter.
For this release we want to give special thanks to the following reporters for the clear reports and tests made after our fixes:

    +
  • Tuukka Mustonen (tuukka.mustonen at gmail.com) who gave us a lot of useful feedback which helped resolve + Bug + 60689 and + Bug + 60690
    • +
  • Amar Darisa (amar.darisa at gmail.com) who helped us with his feedback on + Bug + 60682

Apologies if we have omitted anyone else. @@ -816,7 +880,13 @@ Apologies if we have omitted anyone else

Known problems and workarounds

- +
  • The Once Only controller behaves correctly under a Thread Group or Loop Controller, but otherwise its behaviour is not consistent (or clearly specified).
    • @@ -829,17 +899,6 @@ the total number of threads only applies
  • -Note that there is a bug in Java -on some Linux systems that manifests itself as the following error when running the test cases or JMeter itself: -
    - [java] WARNING: Couldn't flush user prefs:
- java.util.prefs.BackingStoreException:
- java.lang.IllegalArgumentException: Not supported: indent-number
-
    -This does not affect JMeter operation. This issue is fixed since Java 7b05. -
    • - -
  • Note that under some windows systems you may have this WARNING: 
     java.util.prefs.WindowsPreferences
@@ -850,17 +909,11 @@ The fix is to run JMeter as Administrato
  • -With Oracle Java 7 and Mac Book Pro Retina Display, the JMeter GUI may look blurry. -This is a known Java bug, see Bug JDK-8000629. -A workaround is to use a Java 7 update 40 runtime which fixes this issue. -
    • - -
  • You may encounter the following error: 
    java.security.cert.CertificateException: Certificates does not conform to algorithm constraints
    if you run a HTTPS request on a web site with a SSL certificate (itself or one of SSL certificates in its chain of trust) with a signature algorithm using MD2 (like md2WithRSAEncryption) or with a SSL certificate with a size lower than 1024 bits. -This error is related to increased security in Java 7 version u16 (MD2) and version u40 (Certificate size lower than 1024 bits), and Java 8 too. +This error is related to increased security in Java 8+.
    To allow you to perform your HTTPS request, you can downgrade the security of your Java installation by editing the Java jdk.certpath.disabledAlgorithms property. Remove the MD2 value or the constraint on size, depending on your case. @@ -875,7 +928,7 @@ See JDK-8065373 -The fix is to use JDK7_u79, JDK8_u45 or later. +The fix is to use JDK8_u45 or later.
  • @@ -884,7 +937,7 @@ View Results Tree may fail to display so 54586. This is due to a known Java bug which fails to parse "px" units in row/col attributes. See Bug JDK-8031109 -The fix is to use JDK9 b65 or later. +The fix is to use JDK9 b65 or later (but be aware that Java 9 is not certified yet for JMeter).
  • @@ -899,7 +952,7 @@ The fix is to use JDK 8 b132 or later.
Copyright © 1999 – - 2016 + 2017 , Apache Software Foundation
Apache, Apache JMeter, JMeter, the Apache feather, and the Apache JMeter logo are