Author: sebb
Date: Tue Oct 7 09:26:22 2008
New Revision: 702533
URL: http://svn.apache.org/viewvc?rev=702533&view=rev
Log:
Add comments re firewalls and reverse connections
Modified:
jakarta/jmeter/trunk/xdocs/usermanual/remote-test.xml
Modified: jakarta/jmeter/trunk/xdocs/usermanual/remote-test.xml
URL:
http://svn.apache.org/viewvc/jakarta/jmeter/trunk/xdocs/usermanual/remote-test.xml?rev=702533&r1=702532&r2=702533&view=diff
==============================================================================
--- jakarta/jmeter/trunk/xdocs/usermanual/remote-test.xml (original)
+++ jakarta/jmeter/trunk/xdocs/usermanual/remote-test.xml Tue Oct 7 09:26:22
2008
@@ -125,6 +125,14 @@
<p>Steps 2 and 3 remain the same.</p>
</subsection>
<subsection name="§-num;.2 Tips" anchor="tips">
+<p>
+JMeter/RMI requires a connection from the client to the server. This will use
the port you chose, default 1099.
+JMeter/RMI also requires a reverse connection in order to return sample
results from the server to the client.
+This will use a high-numbered port.
+If there are any firewalls or other network filters between JMeter client and
server,
+you will need to make sure that they are set up to allow the connections
through.
+If necessary, use monitoring software to show what traffic is being generated.
+</p>
<p>If you're running Suse Linux, these tips may help. The default installation
may enable the firewall. In that case, remote testing will not work properly.
The following tips were contributed by Sergey Ten.</p>
<p>If you see connections refused, turn on debugging by passing the following
options.</p>
rmiregistry -J-Dsun.rmi.log.debug=true
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
