You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by se...@apache.org on 2007/09/23 03:23:47 UTC

svn commit: r578535 - in /jakarta/jmeter/branches/rel-2-2/docs: ./ images/screenshots/ images/screenshots/webtest/ localising/ usermanual/

Author: sebb
Date: Sat Sep 22 18:23:47 2007
New Revision: 578535

URL: http://svn.apache.org/viewvc?rev=578535&view=rev
Log:
Synch recent document changes

Modified:
    jakarta/jmeter/branches/rel-2-2/docs/changes.html
    jakarta/jmeter/branches/rel-2-2/docs/images/screenshots/sample_result_config.png
    jakarta/jmeter/branches/rel-2-2/docs/images/screenshots/table_results.png
    jakarta/jmeter/branches/rel-2-2/docs/images/screenshots/webtest/http-request.png
    jakarta/jmeter/branches/rel-2-2/docs/localising/index.html
    jakarta/jmeter/branches/rel-2-2/docs/usermanual/component_reference.html
    jakarta/jmeter/branches/rel-2-2/docs/usermanual/get-started.html
    jakarta/jmeter/branches/rel-2-2/docs/usermanual/remote-test.html

Modified: jakarta/jmeter/branches/rel-2-2/docs/changes.html
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/docs/changes.html?rev=578535&r1=578534&r2=578535&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/docs/changes.html (original)
+++ jakarta/jmeter/branches/rel-2-2/docs/changes.html Sat Sep 22 18:23:47 2007
@@ -172,6 +172,16 @@
 						</li>
 									
 
+												<li	>
+								Bug 43449 - Statistical Remote mode does not handle Latency
+						</li>
+									
+
+												<li	>
+								Bug 43450 (partial fix) - Allow SampleCount and ErrorCount to be saved to/restored from files
+						</li>
+									
+
 						</ul>
 							  									 				<h4	>
 								Improvements
@@ -199,6 +209,11 @@
 						</li>
 									
 
+												<li	>
+								Look for user.properties and system.properties in JMeter bin directory if not found locally
+						</li>
+									
+
 						</ul>
 							  									 				<h4	>
 								Fixes since 2.3RC3
@@ -556,7 +571,7 @@
 						</p>
 							  									 				<p	>
 								
-Bug 41104: JMeterThread behaviour was changed so that PostProcessors are run in forward order
+Bug 41140: JMeterThread behaviour was changed so that PostProcessors are run in forward order
 (as they appear in the test plan) rather than reverse order as previously.
 The original behaviour can be restored by setting the following JMeter property:
 
@@ -1085,6 +1100,11 @@
 
 												<li	>
 								Fix ClassCast Exception when using sampler that returns null, e..g TestAction
+						</li>
+									
+
+												<li	>
+								Bug 41140 - Post-processors are run in reverse order
 						</li>
 									
 

Modified: jakarta/jmeter/branches/rel-2-2/docs/images/screenshots/sample_result_config.png
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/docs/images/screenshots/sample_result_config.png?rev=578535&r1=578534&r2=578535&view=diff
==============================================================================
Binary files - no diff available.

Modified: jakarta/jmeter/branches/rel-2-2/docs/images/screenshots/table_results.png
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/docs/images/screenshots/table_results.png?rev=578535&r1=578534&r2=578535&view=diff
==============================================================================
Binary files - no diff available.

Modified: jakarta/jmeter/branches/rel-2-2/docs/images/screenshots/webtest/http-request.png
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/docs/images/screenshots/webtest/http-request.png?rev=578535&r1=578534&r2=578535&view=diff
==============================================================================
Binary files - no diff available.

Modified: jakarta/jmeter/branches/rel-2-2/docs/localising/index.html
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/docs/localising/index.html?rev=578535&r1=578534&r2=578535&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/docs/localising/index.html (original)
+++ jakarta/jmeter/branches/rel-2-2/docs/localising/index.html Sat Sep 22 18:23:47 2007
@@ -212,11 +212,11 @@
 						</a>
 									
 stating your intention. Surely one of the project contributors will be very happy to grab the current texts
-from CVS and send them to you. You'll receive a jar, zip, tar or tgz file that you'll need to unpack in your
+from SVN and send them to you. You'll receive a jar, zip, tar or tgz file that you'll need to unpack in your
 local disk.
 						</p>
 							  									 				<p	>
-								If you are familiar with CVS or you're brave, feel free to anonymously connect to the Jakarta CVS server
+								If you are familiar with SVN or you're brave, feel free to anonymously connect to the Jakarta SVN server
 and obtain the JMeter source yourself, as described in
 
 												<a	 href="http://jakarta.apache.org/site/cvsindex.html">
@@ -244,7 +244,7 @@
 		<tr><td>
 		  <blockquote>
 		  									 				<p	>
-								If you have access to JMeter's CVS repository and you want to pack the files necessary for localisation
+								If you have access to JMeter's SVN repository and you want to pack the files necessary for localisation
 for sending to a translator, just go to the directory above the project root and issue the following command:
 												<br	>
 						</br>
@@ -437,7 +437,7 @@
 									
 
 												<li	>
-								Close i18nEdit and commit to CVS as usual (remember to Refresh your project if you're using Eclipse).
+								Close i18nEdit and commit to SVN as usual (remember to Refresh your project if you're using Eclipse).
 						</li>
 									
 

Modified: jakarta/jmeter/branches/rel-2-2/docs/usermanual/component_reference.html
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/docs/usermanual/component_reference.html?rev=578535&r1=578534&r2=578535&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/docs/usermanual/component_reference.html (original)
+++ jakarta/jmeter/branches/rel-2-2/docs/usermanual/component_reference.html Sat Sep 22 18:23:47 2007
@@ -595,7 +595,7 @@
 									
 
 														<p><b>Control Panel</b></p>
-						<div align="center"><img width='558' height='600' src="../images/screenshots/webtest/http-request.png"></div>
+						<div align="center"><img width='688' height='592' src="../images/screenshots/webtest/http-request.png"></div>
 											  									 			 <p>
 	<b>Parameters</b>
 	<table border="1" cellspacing="0" cellpadding="2">
@@ -696,6 +696,16 @@
 								</td>
 		</tr>
 			<tr>
+			<td>Use multipart/form-data for HTTP POST</td>
+			<td>						
+        Use a multipart/form-data or application/x-www-form-urlencoded post request
+        
+			</td>
+			<td>
+											Yes
+								</td>
+		</tr>
+			<tr>
 			<td>Path</td>
 			<td>						The path to resource (for example, /servlets/myServlet). If the
 resource requires query string parameters, add them below in the
@@ -1775,7 +1785,7 @@
 						</p>
 									 
 														<p><b>Control Panel</b></p>
-						<div align="center"><img width='594' height='309' src="../images/screenshots/ldapext_request.png"></div>
+						<div align="center"><img width='595' height='542' src="../images/screenshots/ldapext_request.png"></div>
 											  									 				<p	>
 								There are nine test operations defined. These operations are given below:
 						</p>
@@ -2615,7 +2625,7 @@
 									
 			
 												<li	>
-								vars - JMeterVariables  - e.g. vars.get("VAR1"); vars.put("VAR2","value"); vars.remove("VAR3");
+								vars - JMeterVariables  - e.g. vars.get("VAR1"); vars.put("VAR2","value"); vars.remove("VAR3"); vars.putObject("OBJ1",new Object());
 						</li>
 									
 		
@@ -2831,7 +2841,7 @@
 									
 
 												<li	>
-								vars - JMeterVariables  - e.g. vars.get("VAR1"); vars.put("VAR2","value"); vars.remove("VAR3");
+								vars - JMeterVariables  - e.g. vars.get("VAR1"); vars.put("VAR2","value"); vars.remove("VAR3"); vars.putObject("OBJ1",new Object());
 						</li>
 									
 
@@ -5267,7 +5277,7 @@
 The saving and reading of test results is generic.  The various
 listeners have a panel whereby one can specify the file to
 which the results will be written (or read from).
-By default, the results are stored as CSV
+By default, the results are stored as XML
 files, typically with a ".jtl" extension.  Storing as CSV is the most efficient option, but is less detailed than XML (the other available option).
 						</p>
 									
@@ -5281,10 +5291,10 @@
 
 												<p	>
 								Results can be read from XML or CSV format files.
-When reading from CSV results files, the header (if present) is ignored.
+When reading from CSV results files, the header (if present) is used to determine which fields are present.
 
 												<b	>
-								In order to interpret a CSV file correctly, the appropriate properties must be set in jmeter.properties.
+								In order to interpret a header-less CSV file correctly, the appropriate properties must be set in jmeter.properties.
 						</b>
 									
 
@@ -5348,12 +5358,7 @@
 									
 
 												<p	>
-								jmeter.save.saveservice.output_format=csv
-						</p>
-									
-
-												<p	>
-								Change "csv" to "xml" for greater detail.
+								jmeter.save.saveservice.output_format=
 						</p>
 									
 
@@ -5368,8 +5373,7 @@
 
 												<p	>
 								
-One can get a more selective set of information my modifying the
-jmeter.properties file.  The following example indicates how to set
+The following example indicates how to set
 properties to get a vertical bar ("|") delimited format that will
 output results like:.
 						</p>
@@ -5522,22 +5526,22 @@
 								
 
 												<li	>
-								 t - elapsed time (ms)
+								by - bytes in responses
 						</li>
 									
 
 												<li	>
-								lt - latency = time to initial response (ms)
+								de - data encoding
 						</li>
 									
 
 												<li	>
-								ts - timestamp (ms since 1970)
+								dt - data type
 						</li>
 									
 
 												<li	>
-								 s - successful (true/false)
+								ec - error count (0 or 1, unless multiple samples are aggregated)
 						</li>
 									
 
@@ -5547,6 +5551,21 @@
 									
 
 												<li	>
+								lt - latency = time to initial response (ms)
+						</li>
+									
+
+												<li	>
+								na - number of active threads in all thread groups
+						</li>
+									
+
+												<li	>
+								ng - number of active threads in current thread group
+						</li>
+									
+
+												<li	>
 								rc - response code (e.g. 200)
 						</li>
 									
@@ -5557,17 +5576,27 @@
 									
 
 												<li	>
-								tn - thread name
+								 s - successful (true/false)
 						</li>
 									
 
 												<li	>
-								dt - data type
+								sc - sample count (1, unless multiple samples are aggregated)
 						</li>
 									
 
 												<li	>
-								de - data encoding
+								 t - elapsed time (ms)
+						</li>
+									
+
+												<li	>
+								tn - thread name
+						</li>
+									
+
+												<li	>
+								ts - timestamp (ms since 1970)
 						</li>
 									
 
@@ -5575,7 +5604,7 @@
 									
 
 														<p><b>Control Panel</b></p>
-						<div align="center"><img width='767' height='252' src="../images/screenshots/sample_result_config.png"></div>
+						<div align="center"><img width='767' height='276' src="../images/screenshots/sample_result_config.png"></div>
 											  		</td></tr>
 		<tr><td><br></td></tr>
 	 </table>
@@ -5882,14 +5911,13 @@
 		  </font>
 		</td></tr>
 				<tr><td>
-		  															This visualizer creates a row for every sample result.  Each sample result's URL,
-time in milliseconds, success/failure is displayed.  Like the 
+		  															This visualizer creates a row for every sample result.  
+Like the 
 												<a href="../usermanual/component_reference.html#View_Results_Tree">View Results Tree</a>
-									,
-this visualizer uses a lot of memory. The last column shows the number of bytes for the
-response from the server.
+									, this visualizer uses a lot of memory.
+
 														<p><b>Control Panel</b></p>
-						<div align="center"><img width='643' height='678' src="../images/screenshots/table_results.png"></div>
+						<div align="center"><img width='658' height='700' src="../images/screenshots/table_results.png"></div>
 											  		</td></tr>
 		<tr><td><br></td></tr>
 	 </table>
@@ -5903,7 +5931,11 @@
 				<tr><td>
 		  															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.
+recording data by eliminating GUI overhead.
+When running in non-GUI mode, the -l flag can be used to create a data file.
+The fields to save are defined by JMeter properties.
+See the jmeter.properties file for details.
+
 														<p><b>Control Panel</b></p>
 						<div align="center"><img width='649' height='157' src="../images/screenshots/simpledatawriter.png"></div>
 											  		</td></tr>
@@ -6204,7 +6236,7 @@
 									
 
 												<li	>
-								vars - (JMeterVariables) - gives read/write access to variables: vars.get(key); vars.put(key,val)
+								vars - (JMeterVariables) - gives read/write access to variables: vars.get(key); vars.put(key,val); vars.putObject("OBJ1",new Object());
 						</li>
 									
 
@@ -8578,7 +8610,7 @@
 									
 	
 												<li	>
-								vars - JMeterVariables  - e.g. vars.get("VAR1"); vars.put("VAR2","value");
+								vars - JMeterVariables  - e.g. vars.get("VAR1"); vars.put("VAR2","value"); vars.putObject("OBJ1",new Object());
 						</li>
 									
 
@@ -9313,7 +9345,7 @@
 									
 
 												<li	>
-								vars - (JMeterVariables) - gives read/write access to variables: vars.get(key); vars.put(key,val)
+								vars - (JMeterVariables) - gives read/write access to variables: vars.get(key); vars.put(key,val); vars.putObject("OBJ1",new Object());
 						</li>
 									
 
@@ -9988,7 +10020,7 @@
 									
 
 												<li	>
-								vars - (JMeterVariables) - gives read/write access to variables: vars.get(key); vars.put(key,val)
+								vars - (JMeterVariables) - gives read/write access to variables: vars.get(key); vars.put(key,val); vars.putObject("OBJ1",new Object());
 						</li>
 									
 
@@ -10689,7 +10721,7 @@
 									
 
 												<li	>
-								vars - (JMeterVariables) - gives read/write access to variables: vars.get(key); vars.put(key,val)
+								vars - (JMeterVariables) - gives read/write access to variables: vars.get(key); vars.put(key,val); vars.putObject("OBJ1",new Object());
 						</li>
 									
 

Modified: jakarta/jmeter/branches/rel-2-2/docs/usermanual/get-started.html
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/docs/usermanual/get-started.html?rev=578535&r1=578534&r2=578535&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/docs/usermanual/get-started.html (original)
+++ jakarta/jmeter/branches/rel-2-2/docs/usermanual/get-started.html Sat Sep 22 18:23:47 2007
@@ -1186,7 +1186,8 @@
 								user.properties
 						</b>
 									.
-  The file will be automatically loaded if it is found in the current directory.
+  The file will be automatically loaded if it is found in the current directory
+  or if it is found in the JMeter bin directory.
   Similarly, 
 												<b	>
 								system.properties

Modified: jakarta/jmeter/branches/rel-2-2/docs/usermanual/remote-test.html
URL: http://svn.apache.org/viewvc/jakarta/jmeter/branches/rel-2-2/docs/usermanual/remote-test.html?rev=578535&r1=578534&r2=578535&view=diff
==============================================================================
--- jakarta/jmeter/branches/rel-2-2/docs/usermanual/remote-test.html (original)
+++ jakarta/jmeter/branches/rel-2-2/docs/usermanual/remote-test.html Sat Sep 22 18:23:47 2007
@@ -444,6 +444,77 @@
 		</td></tr>
 		<tr><td><br></td></tr>
 	 </table>
+							  									 			 	 <table border="0" cellspacing="0" cellpadding="2" width="100%">
+		<tr><td bgcolor="#828DA6">
+		  <font color="#ffffff" face="arial,helvetica,sanserif">
+			 <a name="batchmode"><strong>15.4 Using sample batching</strong></a>
+		  </font>
+		</td></tr>
+		<tr><td>
+		  <blockquote>
+		  									 				<p	>
+								
+Listeners in the test plan send their results back to the client JMeter which writes the results to the specified files
+By default, samples are sent back as they are generated. This can place a large load on the network and the JMeter client.
+There are some JMeter properties that can be set to alter this behaviour.
+
+						</p>
+							  									 				<ul	>
+								
+
+												<li	>
+								mode - sample sending mode - default is Standard
+						</li>
+									
+    
+												<ul	>
+								
+    
+												<li	>
+								Standard - send samples as soon as they are generated
+						</li>
+									
+    
+												<li	>
+								Hold - hold samples in an array until the end of a run. This may use a lot of memory on the server.
+						</li>
+									
+    
+												<li	>
+								Batch - send saved samples when either the count or time exceeds a threshold
+						</li>
+									
+    
+												<li	>
+								Statistical - send a summary report when either the count or time exceeds a threshold
+						</li>
+									
+    
+						</ul>
+									
+
+						</ul>
+							  									 				<p	>
+								The following properties apply to the Batch and Statistical modes:
+						</p>
+							  									 				<ul	>
+								
+    
+												<li	>
+								num_sample_threshold - number of samples in a batch (default 100)
+						</li>
+									
+    
+												<li	>
+								time_threshold - number of milliseconds to wait (default 60 seconds)
+						</li>
+									
+    
+						</ul>
+							  		  </blockquote>
+		</td></tr>
+		<tr><td><br></td></tr>
+	 </table>
 							  		  </blockquote>
 		  </p>
 		</td></tr>



---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org