xdocs/changes.xml - jmeter - Git at Google

 <?xml version="1.0"?>
 <!--
   ~ Licensed to the Apache Software Foundation (ASF) under one or more
   ~ contributor license agreements.  See the NOTICE file distributed with
   ~ this work for additional information regarding copyright ownership.
   ~ The ASF licenses this file to you under the Apache License, Version 2.0
   ~ (the "License"); you may not use this file except in compliance with
   ~ the License.  You may obtain a copy of the License at
   ~
   ~ http://www.apache.org/licenses/LICENSE-2.0
   ~
   ~ Unless required by applicable law or agreed to in writing, software
   ~ distributed under the License is distributed on an "AS IS" BASIS,
   ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   ~ See the License for the specific language governing permissions and
   ~ limitations under the License.
   -->

 <!DOCTYPE document
 [
 <!ENTITY hellip   "&#x02026;">
 <!ENTITY le       "&#x02264;">
 <!ENTITY nbsp     "&#x000A0;">
 <!ENTITY ndash    "&#x02013;">
 <!ENTITY oacute   "&#x000F3;">
 <!ENTITY rarr     "&#x02192;">
 <!ENTITY rArr     "&#x021D2;">
 <!ENTITY THORN    "&#x000DE;">
 <!ENTITY vellip   "&#x022EE;">
 ]>
 <document>
 <properties>
     <author email="dev AT jmeter.apache.org">JMeter developers</author>
     <title>Changes</title>
 </properties>
 <body>
 <section name="Changes">
 <style type="text/css"><!--
 h2 { color: #960000; }
 h3 { color: #960000; }
 --></style>
 <note>
 <b>This page details the changes made in the current version only.</b>
 <br></br>
 Earlier changes are detailed in the <a href="changes_history.html">History of Previous Changes</a>.
 </note>

 <br></br>
 <note>
 JMeter 6.x requires Java 17 or later for execution (Java 21 is recommended).
 </note>

 <!--  =================== 6.0.0 =================== -->

 <h1>Version 6.0.0 </h1>
 <p>
 Summary
 </p>
 <ul>
 <li><a href="#Changes">Changes</a></li>
 </ul>

   <ch_section>Changes</ch_section>
   <h3>General</h3>
   <ul>
     <li><pr>6220</pr> Require Java 17 or later for running JMeter</li>
     <li><pr>6550</pr> Require Kotlin 1.9 or later for running JMeter</li>
     <li><pr>6274</pr> Change references to old MySQL driver to new class <code>com.mysql.cj.jdbc.Driver</code></li>
     <li><issue>6352</issue> Calculate delays in Open Model Thread Group and Precise Throughput
         Timer relative to start of Thread Group instead of the start of the test.</li>
     <li><issue>6357</issue><pr>6358</pr> Ensure writable directories when copying template files while report generation.</li>
   </ul>

   <h3>HTTP Samplers and Test Script Recorder</h3>
   <ul>
     <li><pr>5891</pr>Skip Internet Explorer 6-9 conditional comment processing when fetching resource links</li>
   </ul>

  <!--  =================== Thanks =================== -->

 <ch_section>Thanks</ch_section>
 <p>We thank all contributors mentioned in bug and improvement sections above:
 </p>
 <ul>
 </ul>
 <p>We also thank bug reporters who helped us improve JMeter.</p>
 <ul>
 </ul>
 <p>
 Apologies if we have omitted anyone else.
 </p>
  <!--  =================== Known bugs or issues related to JAVA Bugs =================== -->

 <ch_section>Known problems and workarounds</ch_section>
 <ul>
 <li>The Once Only controller behaves correctly under a Thread Group or Loop Controller,
 but otherwise its behaviour is not consistent (or clearly specified).</li>

 <li>
 The numbers that appear to the left of the green box are the number of active threads / total number of threads,
 the total number of threads only applies to a locally run test, otherwise it will show <code>0</code> (see <bugzilla>55510</bugzilla>).
 </li>

 <li>
 Note that under some windows systems you may have this WARNING:
 <source>
 java.util.prefs.WindowsPreferences
 WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0
 x80000002. Windows RegCreateKeyEx(&hellip;) returned error code 5.
 </source>
 The fix is to run JMeter as Administrator, it will create the registry key for you, then you can restart JMeter as a normal user and you won't have the warning anymore.
 </li>

 <li>
 You may encounter the following error:
 <source>java.security.cert.CertificateException: Certificates does not conform to algorithm constraints</source>
  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 <code>md2WithRSAEncryption</code>) or with a SSL certificate with a size lower than 1024 bits.
 This error is related to increased security in Java 8+.
 <br></br>
 To allow you to perform your HTTPS request, you can downgrade the security of your Java installation by editing
 the Java <code>jdk.certpath.disabledAlgorithms</code> property. Remove the MD2 value or the constraint on size, depending on your case.
 <br></br>
 This property is in this file:
 <source>JAVA_HOME/jre/lib/security/java.security</source>
 See  <bugzilla>56357</bugzilla> for details.
 </li>

 <li>
 Since Java 11 the JavaScript implementation <a href="https://openjdk.java.net/jeps/335">Nashorn has been deprecated</a>.
 Java will emit the following deprecation warnings, if you are using JavaScript based on Nashorn.
 <source>
 Warning: Nashorn engine is planned to be removed from a future JDK release
 </source>
 To silence these warnings, add <code>-Dnashorn.args=--no-deprecation-warning</code> to your Java arguments.
 That can be achieved by setting the enviroment variable <code>JVM_ARGS</code>
 <source>
 export JVM_ARGS="-Dnashorn.args=--no-deprecation-warning"
 </source>
 </li>

 <li>
 With Java 15 the JavaScript implementation <a href="https://openjdk.java.net/jeps/372">Nashorn has been removed</a>. To add back a JSR-223 compatible JavaScript engine you have two options:
   <dl>
     <dt>Use Mozilla Rhino</dt>
     <dd>Copy <a href="https://github.com/mozilla/rhino/releases/download/Rhino1_7_14_Release/rhino-engine-1.7.14.jar">rhino-engine-1.7.14.jar</a> into <code>$JMETER_HOME/lib/ext</code>.</dd>
     <dt>Use OpenJDK Nashorn</dt>
     <dd>
       The OpenJDK Nashorn implementation comes as a module. To use it, you will have to download it and add it to the module path. A hacky way to download the version 15.0 (or later) and its dependencies and set the module path is outlined below:
       <source>
 mkdir lib/modules
 pushd lib/modules
 wget https://repo1.maven.org/maven2/org/openjdk/nashorn/nashorn-core/15.4/nashorn-core-15.4.jar
 wget https://repo1.maven.org/maven2/org/ow2/asm/asm/9.6/asm-9.6.jar
 wget https://repo1.maven.org/maven2/org/ow2/asm/asm-commons/9.6/asm-commons-9.6.jar
 wget https://repo1.maven.org/maven2/org/ow2/asm/asm-util/9.6/asm-util-9.6.jar
 wget https://repo1.maven.org/maven2/org/ow2/asm/asm-tree/9.6/asm-tree-9.6.jar
 wget https://repo1.maven.org/maven2/org/ow2/asm/asm-analysis/9.6/asm-analysis-9.6.jar
 popd
 export JVM_ARGS="--module-path $PWD/lib/modules"
 ./bin/jmeter
       </source>
     </dd>
   </dl>
 </li>

 </ul>

 </section>
 </body>
 </document>
	<?xml version="1.0"?>
	<!--
	~ Licensed to the Apache Software Foundation (ASF) under one or more
	~ contributor license agreements. See the NOTICE file distributed with
	~ this work for additional information regarding copyright ownership.
	~ The ASF licenses this file to you under the Apache License, Version 2.0
	~ (the "License"); you may not use this file except in compliance with
	~ the License. You may obtain a copy of the License at
	~
	~ http://www.apache.org/licenses/LICENSE-2.0
	~
	~ Unless required by applicable law or agreed to in writing, software
	~ distributed under the License is distributed on an "AS IS" BASIS,
	~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
	~ See the License for the specific language governing permissions and
	~ limitations under the License.
	-->

	<!DOCTYPE document
	[
	<!ENTITY hellip "…">
	<!ENTITY le "≤">
	<!ENTITY nbsp " ">
	<!ENTITY ndash "–">
	<!ENTITY oacute "ó">
	<!ENTITY rarr "→">
	<!ENTITY rArr "⇒">
	<!ENTITY THORN "Þ">
	<!ENTITY vellip "⋮">
	]>
	<document>
	<properties>
	<author email="dev AT jmeter.apache.org">JMeter developers</author>
	<title>Changes</title>
	</properties>
	<body>
	<section name="Changes">
	<style type="text/css"><!--
	h2 { color: #960000; }
	h3 { color: #960000; }
	--></style>
	<note>
	<b>This page details the changes made in the current version only.</b>
	<br></br>
	Earlier changes are detailed in the <a href="changes_history.html">History of Previous Changes</a>.
	</note>

	<br></br>
	<note>
	JMeter 6.x requires Java 17 or later for execution (Java 21 is recommended).
	</note>

	<!-- =================== 6.0.0 =================== -->

	<h1>Version 6.0.0 </h1>
	<p>
	Summary
	</p>
	<ul>
	<li><a href="#Changes">Changes</a></li>
	</ul>

	<ch_section>Changes</ch_section>
	<h3>General</h3>
	<ul>
	<li><pr>6220</pr> Require Java 17 or later for running JMeter</li>
	<li><pr>6550</pr> Require Kotlin 1.9 or later for running JMeter</li>
	<li><pr>6274</pr> Change references to old MySQL driver to new class <code>com.mysql.cj.jdbc.Driver</code></li>
	<li><issue>6352</issue> Calculate delays in Open Model Thread Group and Precise Throughput
	Timer relative to start of Thread Group instead of the start of the test.</li>
	<li><issue>6357</issue><pr>6358</pr> Ensure writable directories when copying template files while report generation.</li>
	</ul>

	<h3>HTTP Samplers and Test Script Recorder</h3>
	<ul>
	<li><pr>5891</pr>Skip Internet Explorer 6-9 conditional comment processing when fetching resource links</li>
	</ul>

	<!-- =================== Thanks =================== -->

	<ch_section>Thanks</ch_section>
	<p>We thank all contributors mentioned in bug and improvement sections above:
	</p>
	<ul>
	</ul>
	<p>We also thank bug reporters who helped us improve JMeter.</p>
	<ul>
	</ul>
	<p>
	Apologies if we have omitted anyone else.
	</p>
	<!-- =================== Known bugs or issues related to JAVA Bugs =================== -->

	<ch_section>Known problems and workarounds</ch_section>
	<ul>
	<li>The Once Only controller behaves correctly under a Thread Group or Loop Controller,
	but otherwise its behaviour is not consistent (or clearly specified).</li>

	<li>
	The numbers that appear to the left of the green box are the number of active threads / total number of threads,
	the total number of threads only applies to a locally run test, otherwise it will show <code>0</code> (see <bugzilla>55510</bugzilla>).
	</li>

	<li>
	Note that under some windows systems you may have this WARNING:
	<source>
	java.util.prefs.WindowsPreferences
	WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0
	x80000002. Windows RegCreateKeyEx(…) returned error code 5.
	</source>
	The fix is to run JMeter as Administrator, it will create the registry key for you, then you can restart JMeter as a normal user and you won't have the warning anymore.
	</li>

	<li>
	You may encounter the following error:
	<source>java.security.cert.CertificateException: Certificates does not conform to algorithm constraints</source>
	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 <code>md2WithRSAEncryption</code>) or with a SSL certificate with a size lower than 1024 bits.
	This error is related to increased security in Java 8+.
	<br></br>
	To allow you to perform your HTTPS request, you can downgrade the security of your Java installation by editing
	the Java <code>jdk.certpath.disabledAlgorithms</code> property. Remove the MD2 value or the constraint on size, depending on your case.
	<br></br>
	This property is in this file:
	<source>JAVA_HOME/jre/lib/security/java.security</source>
	See <bugzilla>56357</bugzilla> for details.
	</li>

	<li>
	Since Java 11 the JavaScript implementation <a href="https://openjdk.java.net/jeps/335">Nashorn has been deprecated</a>.
	Java will emit the following deprecation warnings, if you are using JavaScript based on Nashorn.
	<source>
	Warning: Nashorn engine is planned to be removed from a future JDK release
	</source>
	To silence these warnings, add <code>-Dnashorn.args=--no-deprecation-warning</code> to your Java arguments.
	That can be achieved by setting the enviroment variable <code>JVM_ARGS</code>
	<source>
	export JVM_ARGS="-Dnashorn.args=--no-deprecation-warning"
	</source>
	</li>

	<li>
	With Java 15 the JavaScript implementation <a href="https://openjdk.java.net/jeps/372">Nashorn has been removed</a>. To add back a JSR-223 compatible JavaScript engine you have two options:
	<dl>
	<dt>Use Mozilla Rhino</dt>
	<dd>Copy <a href="https://github.com/mozilla/rhino/releases/download/Rhino1_7_14_Release/rhino-engine-1.7.14.jar">rhino-engine-1.7.14.jar</a> into <code>$JMETER_HOME/lib/ext</code>.</dd>
	<dt>Use OpenJDK Nashorn</dt>
	<dd>
	The OpenJDK Nashorn implementation comes as a module. To use it, you will have to download it and add it to the module path. A hacky way to download the version 15.0 (or later) and its dependencies and set the module path is outlined below:
	<source>
	mkdir lib/modules
	pushd lib/modules
	wget https://repo1.maven.org/maven2/org/openjdk/nashorn/nashorn-core/15.4/nashorn-core-15.4.jar
	wget https://repo1.maven.org/maven2/org/ow2/asm/asm/9.6/asm-9.6.jar
	wget https://repo1.maven.org/maven2/org/ow2/asm/asm-commons/9.6/asm-commons-9.6.jar
	wget https://repo1.maven.org/maven2/org/ow2/asm/asm-util/9.6/asm-util-9.6.jar
	wget https://repo1.maven.org/maven2/org/ow2/asm/asm-tree/9.6/asm-tree-9.6.jar
	wget https://repo1.maven.org/maven2/org/ow2/asm/asm-analysis/9.6/asm-analysis-9.6.jar
	popd
	export JVM_ARGS="--module-path $PWD/lib/modules"
	./bin/jmeter
	</source>
	</dd>
	</dl>
	</li>

	</ul>

	</section>
	</body>
	</document>