jmeter-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From milam...@apache.org
Subject svn commit: r1853634 - in /jmeter/trunk/docs: ./ images/screenshots/changes/5.1/ usermanual/
Date Fri, 15 Feb 2019 11:17:33 GMT
Author: milamber
Date: Fri Feb 15 11:17:33 2019
New Revision: 1853634

URL: http://svn.apache.org/viewvc?rev=1853634&view=rev
Log:
Prepare next release 5.1: update docs tree and overview (RC2)

Modified:
    jmeter/trunk/docs/changes.html
    jmeter/trunk/docs/images/screenshots/changes/5.1/jdbc-connection-config-init-request.png
    jmeter/trunk/docs/index.html
    jmeter/trunk/docs/usermanual/best-practices.html
    jmeter/trunk/docs/usermanual/boss.html
    jmeter/trunk/docs/usermanual/build-test-plan.html
    jmeter/trunk/docs/usermanual/component_reference.html
    jmeter/trunk/docs/usermanual/get-started.html
    jmeter/trunk/docs/usermanual/index.html
    jmeter/trunk/docs/usermanual/jmeter_distributed_testing_step_by_step.html
    jmeter/trunk/docs/usermanual/jmeter_proxy_step_by_step.html
    jmeter/trunk/docs/usermanual/listeners.html
    jmeter/trunk/docs/usermanual/properties_reference.html
    jmeter/trunk/docs/usermanual/remote-test.html

Modified: jmeter/trunk/docs/changes.html
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/changes.html?rev=1853634&r1=1853633&r2=1853634&view=diff
==============================================================================
--- jmeter/trunk/docs/changes.html (original)
+++ jmeter/trunk/docs/changes.html Fri Feb 15 11:17:33 2019
@@ -792,6 +792,13 @@ containing a fix to this issue, we decid
       Pull request #437</a>
     -
   Use utf-8 for properties files in source</li>
+    
+<li>
+<a href="https://bz.apache.org/bugzilla/show_bug.cgi?id=63177">
+      Bug
+      63177</a>
+    -
+  Rename NON GUI mode into CLI Mode in documentation</li>
 
 </ul>
 
@@ -1130,6 +1137,13 @@ containing a fix to this issue, we decid
   Apply naming policy does not refresh UI</li>
     
 <li>
+<a href="https://bz.apache.org/bugzilla/show_bug.cgi?id=63180">
+      Bug
+      63180</a>
+    -
+  Apply Naming Policy allows multi selection but only considers first node</li>
+    
+<li>
 <a href="https://bz.apache.org/bugzilla/show_bug.cgi?id=63090">
       Bug
       63090</a>
@@ -1200,16 +1214,6 @@ Apologies if we have omitted anyone else
 
 <ul>
 
-<li>View Results Tree may freeze rendering large response particularly if this response
has no spaces, see <a href="https://bz.apache.org/bugzilla/show_bug.cgi?id=60816">
-      Bug
-      60816</a>.
-This is due to an identified Java Bug <a href="https://bugs.openjdk.java.net/browse/JDK-8172336">UI
stuck when calling <span class="code">JEditorPane.setText()</span> or <span
class="code">JTextArea.setText()</span> with long text without space</a>.
-</li>
-
-</ul>
-
-<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>
 

Modified: jmeter/trunk/docs/images/screenshots/changes/5.1/jdbc-connection-config-init-request.png
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/images/screenshots/changes/5.1/jdbc-connection-config-init-request.png?rev=1853634&r1=1853633&r2=1853634&view=diff
==============================================================================
Binary files - no diff available.

Modified: jmeter/trunk/docs/index.html
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/index.html?rev=1853634&r1=1853633&r2=1853634&view=diff
==============================================================================
--- jmeter/trunk/docs/index.html (original)
+++ jmeter/trunk/docs/index.html Fri Feb 15 11:17:33 2019
@@ -236,7 +236,7 @@
 <li>Full featured Test IDE that allows fast Test Plan <b>recording (from Browsers
or native applications), building and debugging</b>.</li>
     
 <li>
-<b><a href="usermanual/get-started.html#non_gui">Command-line mode (Non GUI /
headless mode)</a></b> to load test from any Java compatible OS (Linux, Windows,
Mac OSX, &hellip;)</li>
+<b><a href="usermanual/get-started.html#non_gui">CLI mode (Command-line mode
(previously called Non GUI) / headless mode)</a></b> to load test from any Java
compatible OS (Linux, Windows, Mac OSX, &hellip;)</li>
     
 <li>A complete and <b><a href="usermanual/generating-dashboard.html">ready
to present dynamic HTML report</a></b>
 </li>

Modified: jmeter/trunk/docs/usermanual/best-practices.html
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/usermanual/best-practices.html?rev=1853634&r1=1853633&r2=1853634&view=diff
==============================================================================
--- jmeter/trunk/docs/usermanual/best-practices.html (original)
+++ jmeter/trunk/docs/usermanual/best-practices.html Fri Feb 15 11:17:33 2019
@@ -214,7 +214,7 @@ You should absolutely avoid using versio
 run with JMeter.  The number will also depend on how fast your server is (a faster server
  makes JMeter work harder since it returns a response quicker).  As with any Load Testing
tool, if you don't correctly size
  the number of threads, you will face the "Coordinated Omission" problem which can give you
wrong or inaccurate results.
- If you need large-scale load testing, consider running multiple non-GUI JMeter instances
on multiple machines 
+ If you need large-scale load testing, consider running multiple CLI JMeter instances on
multiple machines 
  using distributed mode (or not). When using distributed mode the result file is combined
on the Controller node, if
  using multiple autonomous instances, the sample result files can be combined for subsequent
analysis.
 For testing how JMeter performs on a given platform, the JavaTest sampler can be used.
@@ -346,7 +346,7 @@ Some suggestions on reducing resource us
 
 <ul>
 
-<li>Use non-GUI mode: <span class="code">jmeter -n -t test.jmx -l test.jtl</span>
+<li>Use CLI mode: <span class="code">jmeter -n -t test.jmx -l test.jtl</span>
 </li>
 
 <li>Use as few Listeners as possible; if using the <span class="code">-l</span>
flag as above they can all be deleted or disabled.</li>
@@ -451,7 +451,7 @@ bsh % &hellip; disconnected from server.
 </p>
 
 <p>
-As a practical example, assume you have a long-running JMeter test running in non-GUI mode,
+As a practical example, assume you have a long-running JMeter test running in CLI mode,
 and you want to vary the throughput at various times during the test.
 The test-plan includes a Constant Throughput Timer which is defined in terms of a property,
 e.g. <span class="code">${__P(throughput)}</span>.
@@ -609,7 +609,7 @@ To run the test with 20 loops, just chan
 </p>
 
 <p>
-This quickly becomes tedious if you want to run lots of tests in non-GUI mode.
+This quickly becomes tedious if you want to run lots of tests in CLI mode.
 One solution to this is to define the Test Plan variable in terms of a property,
 for example <span class="code">LOOPS=${__P(loops,10)}</span>.
 This uses the value of the property "<span class="code">loops</span>", defaulting
to <span class="code">10</span> if the property is not found.

Modified: jmeter/trunk/docs/usermanual/boss.html
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/usermanual/boss.html?rev=1853634&r1=1853633&r2=1853634&view=diff
==============================================================================
--- jmeter/trunk/docs/usermanual/boss.html (original)
+++ jmeter/trunk/docs/usermanual/boss.html Fri Feb 15 11:17:33 2019
@@ -307,7 +307,7 @@ for the testing account).
 <p>
 Also note that some Linux/Unix editions are intended for server use.
 These generally have minimal or no GUI support.
-Such OSes should be OK for running JMeter in non-GUI mode, but JMeter GUI mode probably won't
work
+Such OSes should be OK for running JMeter in CLI mode, but JMeter GUI mode probably won't
work
 unless you install a minimal GUI environment.
 </p>
 
@@ -323,12 +323,12 @@ JMeter can easily be installed on Cloud
 JMeter is also supported within Commercial Cloud PAAS if you don't want to manage it yourself.

 </p>
 
-<p>Don't forget JMeter batch (NON-GUI) mode. This mode should be used during load testing
for many reasons:
+<p>Don't forget JMeter batch (CLI) mode. This mode should be used during load testing
for many reasons:
 <ul>
 
 <li>If you have a powerful server that supports Java but perhaps does not have a fast
graphics implementation, or where you need to login remotely.</li>
 
-<li>Batch (non-GUI) mode can reduce the network traffic compared with using a remote
display or client-server mode.</li>
+<li>Batch (CLI) mode can reduce the network traffic compared with using a remote display
or client-server mode.</li>
 
 <li>Java AWT Thread used for GUI mode can alter injection behaviour by blocking sometimes</li>
 

Modified: jmeter/trunk/docs/usermanual/build-test-plan.html
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/usermanual/build-test-plan.html?rev=1853634&r1=1853633&r2=1853634&view=diff
==============================================================================
--- jmeter/trunk/docs/usermanual/build-test-plan.html (original)
+++ jmeter/trunk/docs/usermanual/build-test-plan.html Fri Feb 15 11:17:33 2019
@@ -288,7 +288,7 @@ These only apply to a locally run test;
 </p>
 
 <div class="clear"></div>
-<div class="note">Using GUI mode as described here should only be used when debugging
your Test Plan. To run the real load test, use NON-GUI mode.</div>
+<div class="note">Using GUI mode as described here should only be used when debugging
your Test Plan. To run the real load test, use CLI mode.</div>
 <div class="clear"></div>
 
 </div>
@@ -322,8 +322,8 @@ If Shutdown is taking too long. Close th
 </p>
 
 <p>
-When running JMeter in non-GUI mode, there is no Menu, and JMeter does not react to keystrokes
such as <span class="keycombo"><span class="keysym">Control</span>&nbsp;+&nbsp;<span
class="keysym">.</span></span>.
-So JMeter non-GUI mode will listen for commands on a specific port (default <span class="code">4445</span>,
see the JMeter property <span class="code">jmeterengine.nongui.port</span>).
+When running JMeter in CLI mode, there is no Menu, and JMeter does not react to keystrokes
such as <span class="keycombo"><span class="keysym">Control</span>&nbsp;+&nbsp;<span
class="keysym">.</span></span>.
+So JMeter CLI mode will listen for commands on a specific port (default <span class="code">4445</span>,
see the JMeter property <span class="code">jmeterengine.nongui.port</span>).
 JMeter supports automatic choice of an alternate port if the default port is being used 
 (for example by another JMeter instance). In this case, JMeter will try the next higher port,
continuing until
 it reaches the JMeter property <span class="code">jmeterengine.nongui.maxport</span>)
which defaults to <span class="code">4455</span>.

Modified: jmeter/trunk/docs/usermanual/component_reference.html
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/usermanual/component_reference.html?rev=1853634&r1=1853633&r2=1853634&view=diff
==============================================================================
--- jmeter/trunk/docs/usermanual/component_reference.html (original)
+++ jmeter/trunk/docs/usermanual/component_reference.html Fri Feb 15 11:17:33 2019
@@ -4712,7 +4712,7 @@ The "<span class="code">Stop</span>" act
 The "<span class="code">Stop Now</span>" action stops the test without waiting
for samples to complete; it will interrupt any active samples.
 If some threads fail to stop within the 5 second time-limit, a message will be displayed
in GUI mode.
 You can try using the <span class="code">Stop</span> command to see if this will
stop the threads, but if not, you should exit JMeter.
-In non-GUI mode, JMeter will exit if some threads fail to stop within the 5 second time limit.
+In CLI mode, JMeter will exit if some threads fail to stop within the 5 second time limit.
 <div class="clear"></div>
 <div class="note">The time to wait can be changed using the JMeter property <span
class="code">jmeterengine.threadstop.wait</span>. The time is given in milliseconds.</div>
 <div class="clear"></div>
@@ -6826,9 +6826,9 @@ Storing as CSV is the most efficient opt
 
 <p>
 
-<b>Listeners do <i>not</i> process sample data in non-GUI mode, but the
raw data will be saved if an output
+<b>Listeners do <i>not</i> process sample data in CLI mode, but the raw
data will be saved if an output
 file has been configured.</b>
-In order to analyse the data generated by a non-GUI test run, you need to load the file into
the appropriate
+In order to analyse the data generated by a CLI run, you need to load the file into the appropriate
 Listener.
 </p>
 
@@ -7543,7 +7543,7 @@ If this is selected, then the sub-sample
 <div class="description">This listener can record results to a file
 but not to the UI.  It is meant to provide an efficient means of
 recording data by eliminating GUI overhead.
-When running in non-GUI mode, the <span class="code">-l</span> flag can be used
to create a data file.
+When running in CLI mode, the <span class="code">-l</span> flag can be used to
create a data file.
 The fields to save are defined by JMeter properties.
 See the <span class="code">jmeter.properties</span> file for details.
 </div>
@@ -8407,7 +8407,7 @@ time boundary, so that multiple test run
 See <span class="code">jmeter.properties</span> file for the summariser configuration
items:
 <pre class="source">
 # Define the following property to automatically start a summariser with that name
-# (applies to non-GUI mode only)
+# (applies to CLI mode only)
 #summariser.name=summary
 #
 # interval between summaries (in seconds) default 3 minutes
@@ -8419,7 +8419,7 @@ See <span class="code">jmeter.properties
 # Write messages to System.out
 #summariser.out=true
 </pre>
-This element is mainly intended for batch (non-GUI) runs.
+This element is mainly intended for batch (CLI) runs.
 The output looks like the following:
 <pre class="source">
 label +     16 in 0:00:12 =    1.3/s Avg:  1608 Min:  1163 Max:  2009 Err:     0 (0.00%)
Active: 5 Started: 5 Finished: 0
@@ -8467,7 +8467,7 @@ by using suitable labels and adding the
 
 <div class="clear"></div>
 <div class="note">
-In Non-GUI mode by default a Generate Summary Results listener named "<span class="code">summariser</span>"
is configured, if you have already added one to your Test Plan, ensure you name it differently

+In CLI mode by default a Generate Summary Results listener named "<span class="code">summariser</span>"
is configured, if you have already added one to your Test Plan, ensure you name it differently

 otherwise results will be accumulated under this label (summary) leading to wrong results
(sum of total samples + samples located under the Parent of Generate Summary Results listener).<br>
 This is not a bug but a design choice allowing to summarize across thread groups.
 </div>

Modified: jmeter/trunk/docs/usermanual/get-started.html
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/usermanual/get-started.html?rev=1853634&r1=1853633&r2=1853634&view=diff
==============================================================================
--- jmeter/trunk/docs/usermanual/get-started.html (original)
+++ jmeter/trunk/docs/usermanual/get-started.html Fri Feb 15 11:17:33 2019
@@ -254,12 +254,12 @@ The first step is to configure the injec
 
 </ul> 
 
-Once everything is ready, you will use Command-line mode (called <a href="#non_gui">Non-GUI
mode</a>) to run it for the Load Test. 
+Once everything is ready, you will use CLI mode (Command-line mode previously called <a
href="#non_gui">Non-GUI mode</a>) to run it for the Load Test. 
 <div class="clear"></div>
 <div class="note">Don't run load test using GUI mode !</div>
 <div class="clear"></div>
 <br>
-Using Non-GUI mode, you can generate a CSV (or XML) file containing results and have JMeter
<a href="generating-dashboard.html">generate an HTML report</a> at end of Load
Test.
+Using CLI mode, you can generate a CSV (or XML) file containing results and have JMeter <a
href="generating-dashboard.html">generate an HTML report</a> at end of Load Test.
 JMeter will by default provide a summary of load test while it's running. <br>
 You can also have <a href="realtime-results.html">real-time results</a> during
your test using <a href="component_reference.html#Backend_Listener">Backend Listener</a>.
 </p>
@@ -562,7 +562,7 @@ You can rename the parent directory (i.e
 These files are found in the <span class="code">bin</span> directory.
 After a short time, the JMeter GUI should appear.
 <div class="clear"></div>
-<div class="note">GUI mode should only be used for creating the test script, NON GUI
mode must be used for load testing</div>
+<div class="note">GUI mode should only be used for creating the test script, CLI mode
(NON GUI) must be used for load testing</div>
 <div class="clear"></div>
 
 </p>
@@ -588,12 +588,12 @@ Windows script files (the .CMD files req
 <dt>
 <span class="code">jmeter-n.cmd</span>
 </dt>
-<dd>drop a JMX file on this to run a non-GUI test</dd>
+<dd>drop a JMX file on this to run a CLI mode test</dd>
 
 <dt>
 <span class="code">jmeter-n-r.cmd</span>
 </dt>
-<dd>drop a JMX file on this to run a non-GUI test remotely</dd>
+<dd>drop a JMX file on this to run a CLI mode test remotely</dd>
 
 <dt>
 <span class="code">jmeter-t.cmd</span>
@@ -608,17 +608,17 @@ Windows script files (the .CMD files req
 <dt>
 <span class="code">mirror-server.cmd</span>
 </dt>
-<dd>runs the JMeter Mirror Server in non-GUI mode</dd>
+<dd>runs the JMeter Mirror Server in CLI mode</dd>
 
 <dt>
 <span class="code">shutdown.cmd</span>
 </dt>
-<dd>Run the Shutdown client to stop a non-GUI instance gracefully</dd>
+<dd>Run the Shutdown client to stop a CLI mode instance gracefully</dd>
 
 <dt>
 <span class="code">stoptest.cmd</span>
 </dt>
-<dd>Run the Shutdown client to stop a non-GUI instance abruptly</dd>
+<dd>Run the Shutdown client to stop a CLI mode instance abruptly</dd>
 
 </dl>
 
@@ -732,17 +732,17 @@ Un*x script files; should work on most L
 <dt>
 <span class="code">mirror-server.sh</span>
 </dt>
-<dd>runs the JMeter Mirror Server in non-GUI mode</dd>
+<dd>runs the JMeter Mirror Server in CLI mode</dd>
 
 <dt>
 <span class="code">shutdown.sh</span>
 </dt>
-<dd>Run the Shutdown client to stop a non-GUI instance gracefully</dd>
+<dd>Run the Shutdown client to stop a CLI mode instance gracefully</dd>
 
 <dt>
 <span class="code">stoptest.sh</span>
 </dt>
-<dd>Run the Shutdown client to stop a non-GUI instance abruptly</dd>
+<dd>Run the Shutdown client to stop a CLI mode instance abruptly</dd>
 
 </dl>
 
@@ -1059,7 +1059,7 @@ This is not to be confused with the prox
 
 
 <div class="subsection">
-<h2 id="non_gui">1.4.4 Non-GUI Mode (Command Line mode)<a class="sectionlink" href="#non_gui"
title="Link to here">&para;</a>
+<h2 id="non_gui">1.4.4 CLI Mode (Command Line mode was called NON GUI mode)<a class="sectionlink"
href="#non_gui" title="Link to here">&para;</a>
 </h2>
 
 <p>For load testing, you must run JMeter in this mode (Without the GUI) to get the
optimal results from it. To do so, use
@@ -1070,7 +1070,7 @@ the following command options:</p>
 <dt>
 <span class="code">-n</span>
 </dt>
-<dd>This specifies JMeter is to run in non-gui mode</dd>
+<dd>This specifies JMeter is to run in cli mode</dd>
 
 <dt>
 <span class="code">-t</span>
@@ -1148,7 +1148,7 @@ Normally this is not necessary.
 </h2>
 
 <p>For <a href="remote-test.html">distributed testing</a>, run JMeter in
server mode on the remote node(s), and then control the server(s) from the GUI.
-You can also use non-GUI mode to run remote tests.
+You can also use CLI mode to run remote tests.
 To start the server(s), run <span class="code">jmeter-server[.bat]</span> on
each server host.</p>
 
 <p>The script also lets you specify the optional firewall/proxy server information:</p>
@@ -1173,7 +1173,7 @@ To start the server(s), run <span class=
 <p>If you want the server to exit after a single test has been run, then define the
JMeter property <span class="code">server.exitaftertest=true</span>.
 </p>
 
-<p>To run the test from the client in non-GUI mode, use the following command:</p>
+<p>To run the test from the client in CLI mode, use the following command:</p>
 
 <pre class="source">
 jmeter -n -t testplan.jmx -r [-Gprop=val] [-Gglobal.properties] [-X]
@@ -1614,7 +1614,7 @@ These are shown below.</p>
     -d, --homedir &lt;argument&gt;
         the jmeter home directory to use
     -X, --remoteexit
-        Exit the remote servers at end of test (non-GUI)
+        Exit the remote servers at end of test (CLI mode)
     -g, --reportonly &lt;argument&gt;
         generate report dashboard only, from a test results file
     -e, --reportatendofloadtests
@@ -1638,11 +1638,11 @@ that was run in interactive mode.
 
 
 <div class="subsection">
-<h2 id="shutdown">1.4.9 non-GUI shutdown<a class="sectionlink" href="#shutdown"
title="Link to here">&para;</a>
+<h2 id="shutdown">1.4.9 CLI mode shutdown<a class="sectionlink" href="#shutdown"
title="Link to here">&para;</a>
 </h2>
 
 <p>
-Prior to version 2.5.1, JMeter invoked <span class="code">System.exit()</span>
when a non-GUI test completed.
+Prior to version 2.5.1, JMeter invoked <span class="code">System.exit()</span>
when a CLI mode test completed.
 This caused problems for applications that invoke JMeter directly, so JMeter no longer invokes
<span class="code">System.exit()</span>
 for a normal test completion. [Some fatal errors may still invoke <span class="code">System.exit()</span>]
 JMeter will exit all the non-daemon threads it starts, but it is possible that some non-daemon
threads

Modified: jmeter/trunk/docs/usermanual/index.html
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/usermanual/index.html?rev=1853634&r1=1853633&r2=1853634&view=diff
==============================================================================
--- jmeter/trunk/docs/usermanual/index.html (original)
+++ jmeter/trunk/docs/usermanual/index.html Fri Feb 15 11:17:33 2019
@@ -421,7 +421,7 @@
 </li>
         
 <li>
-<a href="get-started.html#non_gui">1.4.4 Non-GUI Mode</a>
+<a href="get-started.html#non_gui">1.4.4 CLI mode</a>
 </li>
         
 <li>
@@ -441,7 +441,7 @@
 </li>
         
 <li>
-<a href="get-started.html#shutdown">1.4.9 non-GUI shutdown</a>
+<a href="get-started.html#shutdown">1.4.9 CLI mode shutdown</a>
 </li>
      
 </ul>

Modified: jmeter/trunk/docs/usermanual/jmeter_distributed_testing_step_by_step.html
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/usermanual/jmeter_distributed_testing_step_by_step.html?rev=1853634&r1=1853633&r2=1853634&view=diff
==============================================================================
--- jmeter/trunk/docs/usermanual/jmeter_distributed_testing_step_by_step.html (original)
+++ jmeter/trunk/docs/usermanual/jmeter_distributed_testing_step_by_step.html Fri Feb 15 11:17:33
2019
@@ -225,7 +225,7 @@ have JMeter installed on all the systems
 
 
 <div class="clear"></div>
-<div class="note">In this tutorial we use GUI Mode just for demonstration. In real
life you should use NON GUI mode to start your load test</div>
+<div class="note">In this tutorial we use GUI Mode just for demonstration. In real
life you should use CLI mode (NON GUI) to start your load test</div>
 <div class="clear"></div>
 
 

Modified: jmeter/trunk/docs/usermanual/jmeter_proxy_step_by_step.html
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/usermanual/jmeter_proxy_step_by_step.html?rev=1853634&r1=1853633&r2=1853634&view=diff
==============================================================================
--- jmeter/trunk/docs/usermanual/jmeter_proxy_step_by_step.html (original)
+++ jmeter/trunk/docs/usermanual/jmeter_proxy_step_by_step.html Fri Feb 15 11:17:33 2019
@@ -531,7 +531,7 @@ ready to run the test, there are two way
 
 
 <p>
-Solution 1, with the gui, but just during debug phase, use Non GUI for your load test.
+Solution 1, with the gui, but just during debug phase, use CLI mode (Non GUI) for your load
test.
 </p>
 
 <p>

Modified: jmeter/trunk/docs/usermanual/listeners.html
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/usermanual/listeners.html?rev=1853634&r1=1853633&r2=1853634&view=diff
==============================================================================
--- jmeter/trunk/docs/usermanual/listeners.html (original)
+++ jmeter/trunk/docs/usermanual/listeners.html Fri Feb 15 11:17:33 2019
@@ -239,7 +239,7 @@ The same filename can be used by multipl
 <p>
 The default items to be saved can be defined in the <span class="code">jmeter.properties</span>
(or <span class="code">user.properties</span>) file.
 The properties are used as the initial settings for the Listener Config pop-up, and are also
-used for the log file specified by the <span class="code">-l</span> command-line
flag (commonly used for non-GUI test runs).
+used for the log file specified by the <span class="code">-l</span> command-line
flag (commonly used for CLI mode test runs).
 </p>
 
 <p>To change the default format, find the following line in <span class="code">jmeter.properties</span>:</p>
@@ -450,11 +450,11 @@ Note that cookies, method and the query
 
 </div>
 <div class="section">
-<h1 id="batch">12.2 non-GUI (batch) test runs<a class="sectionlink" href="#batch"
title="Link to here">&para;</a>
+<h1 id="batch">12.2 CLI mode (batch) test runs<a class="sectionlink" href="#batch"
title="Link to here">&para;</a>
 </h1>
 
 <p>
-When running in non-GUI mode, the <span class="code">-l</span> flag can be used
to create a top-level listener for the test run.
+When running in CLI mode, the <span class="code">-l</span> flag can be used to
create a top-level listener for the test run.
 This is in addition to any Listeners defined in the test plan.
 The configuration of this listener is controlled by entries in the file <span class="code">jmeter.properties</span>
 as described in the previous section.

Modified: jmeter/trunk/docs/usermanual/properties_reference.html
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/usermanual/properties_reference.html?rev=1853634&r1=1853633&r2=1853634&view=diff
==============================================================================
--- jmeter/trunk/docs/usermanual/properties_reference.html (original)
+++ jmeter/trunk/docs/usermanual/properties_reference.html Fri Feb 15 11:17:33 2019
@@ -297,7 +297,7 @@
 <ul></ul>
 </li>
 <li>
-<a href="#summariser">19.26 Summariser - Generate Summary Results - configuration (mainly
applies to non-GUI mode)</a>
+<a href="#summariser">19.26 Summariser - Generate Summary Results - configuration (mainly
applies to CLI mode)</a>
 <ul></ul>
 </li>
 <li>
@@ -3243,7 +3243,7 @@ JMETER-SERVER</pre>
 
 </div>
 <div class="section">
-<h1 id="summariser">19.26 Summariser - Generate Summary Results - configuration (mainly
applies to non-GUI mode)<a class="sectionlink" href="#summariser" title="Link to here">&para;</a>
+<h1 id="summariser">19.26 Summariser - Generate Summary Results - configuration (mainly
applies to CLI mode)<a class="sectionlink" href="#summariser" title="Link to here">&para;</a>
 </h1>
 
 <div class="properties">
@@ -3259,11 +3259,11 @@ JMETER-SERVER</pre>
 <div class="property">
 <div class="name req-true">summariser.name</div>
 <div class="description req-true">
-    Comment the following property to disable the default non-GUI summariser.<br>
+    Comment the following property to disable the default CLI mode summariser.<br>
     [or change the value to rename it]<br>
     
 <div class="clear"></div>
-<div class="note">Applies to non-GUI mode only</div>
+<div class="note">Applies to CLI mode only</div>
 <div class="clear"></div>
     Defaults to: <span class="code">summary</span>
 
@@ -4244,8 +4244,7 @@ JMETER-SERVER</pre>
 <div class="property">
 <div class="name req-true">jmeterengine.stopfail.system.exit</div>
 <div class="description req-true">
-    Whether to call <span class="code">System.exit(1)</span> on failure to stop
threads in
-    non-GUI mode.<br>
+    Whether to call <span class="code">System.exit(1)</span> on failure to stop
threads in CLI mode.<br>
     This only takes effect if the test was explicitly requested to stop.<br>
     If this is disabled, it may be necessary to kill the JVM externally.<br>
     Defaults to: <span class="code">true</span>
@@ -4259,7 +4258,7 @@ JMETER-SERVER</pre>
 <div class="property">
 <div class="name req-true">jmeterengine.force.system.exit</div>
 <div class="description req-true">
-    Whether to force call <span class="code">System.exit(0)</span> at end of
test in non-GUI mode,
+    Whether to force call <span class="code">System.exit(0)</span> at end of
test in CLI mode,
     even if there were no failures and the test was not explicitly asked to stop.<br>
     Without this, the JVM may never exit if there are other threads spawned by
     the test which never exit.<br>
@@ -4288,7 +4287,7 @@ JMETER-SERVER</pre>
 <div class="property">
 <div class="name req-true">jmeterengine.nongui.port</div>
 <div class="description req-true">
-    If running non-GUI, then JMeter listens on the following port for a shutdown message.<br>
+    If running CLI mode, then JMeter listens on the following port for a shutdown message.<br>
     To disable, set the port to <span class="code">1000</span> or less.<br>
     Defaults to: <span class="code">4445</span>
 
@@ -4575,7 +4574,7 @@ JMETER-SERVER</pre>
 <div class="name req-true">classfinder.functions.contain</div>
 <div class="description req-true">
     The classpath finder currently needs to load every single JMeter class to find the classes
it needs.<br>
-    For non-GUI mode, it's only necessary to scan for Function classes, but all classes are
still loaded.<br>
+    For CLI mode, it's only necessary to scan for Function classes, but all classes are still
loaded.<br>
     All current Function classes include "<span class="code">.function.</span>"
in their name, and none include
     "<span class="code">.gui.</span>" in the name, so the number of unwanted
classes loaded can be reduced by
     checking for these. However, if a valid function class name does not match these restrictions,

Modified: jmeter/trunk/docs/usermanual/remote-test.html
URL: http://svn.apache.org/viewvc/jmeter/trunk/docs/usermanual/remote-test.html?rev=1853634&r1=1853633&r2=1853634&view=diff
==============================================================================
--- jmeter/trunk/docs/usermanual/remote-test.html (original)
+++ jmeter/trunk/docs/usermanual/remote-test.html Fri Feb 15 11:17:33 2019
@@ -223,7 +223,7 @@ So if you set 1000 Threads and have 6 JM
 <div class="clear"></div>
 
 <p>
-However, remote mode does use more resources than running the same number of non-GUI tests
independently.
+However, remote mode does use more resources than running the same number of CLI mode tests
independently.
 If many server instances are used, the client JMeter can become overloaded, as can the client
network connection.
 This has been improved by switching to Stripped modes (see below) but you should always check
that your client is not overloaded.
 </p>
@@ -322,11 +322,11 @@ normal JMeter start and stop menu items.
 
 
 <p>
-<b>Step 3b: Start the JMeter from a non-GUI Client</b>
+<b>Step 3b: Start the JMeter from a CLI mode Client</b>
 </p>
 
 <p>
-GUI mode should only be used for debugging, as a better alternative, you should start the
test on remote server(s) from a non-GUI (command-line) client.
+GUI mode should only be used for debugging, as a better alternative, you should start the
test on remote server(s) from a CLI mode (command-line) client.
 The command to do this is:</p>
 
 <pre class="source">



Mime
View raw message