You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jmeter.apache.org by pm...@apache.org on 2014/07/18 19:00:38 UTC
svn commit: r1611712 - /jmeter/trunk/xdocs/usermanual/component_reference.xml
Author: pmouawad
Date: Fri Jul 18 17:00:37 2014
New Revision: 1611712
URL: http://svn.apache.org/r1611712
Log:
Clarify doc on Synchronizing Timer
Modified:
jmeter/trunk/xdocs/usermanual/component_reference.xml
Modified: jmeter/trunk/xdocs/usermanual/component_reference.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/component_reference.xml?rev=1611712&r1=1611711&r2=1611712&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/component_reference.xml (original)
+++ jmeter/trunk/xdocs/usermanual/component_reference.xml Fri Jul 18 17:00:37 2014
@@ -4730,6 +4730,11 @@ points of the test plan.
If timeout in milliseconds is set to 0 and number of threads never reaches "Number of Simultaneous Users to Group by" then Test will pause infinitely.
Only a forced stop will stop it. Setting Timeout in milliseconds is an option to consider in this case.
</note>
+<note>
+Synchronizing timer blocks only within one JVM, so if using Distributed testing ensure you never set "Number of Simultaneous Users to Group by" to a value superior to the number of users
+of its containing Thread group considering 1 injector only.
+</note>
+
</component>
<component name="BeanShell Timer" index="§-num;.6.6" width="846" height="636" screenshot="timers/beanshell_timer.png">