You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Ollie Cook <ol...@betfair.com> on 2005/11/21 16:29:57 UTC
remote testing, different rmi port
Hi,
I am trying to set up remote testing using a different port than 1099
for rmi.
I've started rmiregistry on the client nodes on a different port (13715)
by modifying bin/jmeter-server, and instructed the controller to connect
on that port by means of server_port in jmeter.properties.
However, tcpdump shows the controller trying to communicate on port 1099
still.
Is server_port in jmeter.properties not the correct file to be using?
I've tried setting server.rmi.port to 13715 as well, to no avail.
Thanks,
Ollie
jmeter-server diff on the client nodes
--------------------------------------
$ diff -U1 jmeter-server jmeter-server.new
--- jmeter-server 2005-09-29 22:06:08.000000000 +0000
+++ jmeter-server.new 2005-11-21 15:24:40.000000000 +0000
@@ -21,3 +21,3 @@
export CLASSPATH
-rmiregistry &
+rmiregistry 13715 &
set CLASSPATH=$OLDCLASSPATH
jmeter.properties diff on the controller node
---------------------------------------------
$ diff -U1 jmeter.properties jmeter.properties.new
--- jmeter.properties 2005-09-23 00:10:21.000000000 +0100
+++ jmeter.properties.new 2005-11-21 15:26:16.000000000 +0000
@@ -87,3 +87,3 @@
# Remote Hosts - comma delimited
-remote_hosts=127.0.0.1
+remote_hosts=127.0.0.1,bert.dev.uk.betfair
#remote_hosts:localhost:1099,localhost:2010
@@ -91,3 +91,3 @@
# RMI port to be used by the server
-#server_port=1099
+server_port=13715
@@ -358,3 +358,3 @@
# Change default port used by server (need to start rmiregistry with
same port)
-#server.rmi.port=1099
+server.rmi.port=13715
tcpdump showing connection on 1099/tcp with above configs
---------------------------------------------------------
15:15:26.788354 mutare.32921 > bert.dev.uk.betfair.1099: S
3349072793:3349072793(0) win 5840 <mss 1460,sackOK,timestamp 615613839
0,nop,wscale 2> (DF)
--
Ollie Cook
UNIX Scripter
Information Systems
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: remote testing, different rmi port
Posted by sebb <se...@gmail.com>.
On 21/11/05, Ollie Cook <ol...@betfair.com> wrote:
> Hi,
>
> I am trying to set up remote testing using a different port than 1099
> for rmi.
>
> I've started rmiregistry on the client nodes on a different port (13715)
> by modifying bin/jmeter-server, and instructed the controller to connect
> on that port by means of server_port in jmeter.properties.
>
> However, tcpdump shows the controller trying to communicate on port 1099
> still.
>
> Is server_port in jmeter.properties not the correct file to be using?
> I've tried setting server.rmi.port to 13715 as well, to no avail.
>
> Thanks,
>
> Ollie
>
>
> jmeter-server diff on the client nodes
i.e. the "server" nodes ...
> --------------------------------------
> $ diff -U1 jmeter-server jmeter-server.new
> --- jmeter-server 2005-09-29 22:06:08.000000000 +0000
> +++ jmeter-server.new 2005-11-21 15:24:40.000000000 +0000
> @@ -21,3 +21,3 @@
> export CLASSPATH
> -rmiregistry &
> +rmiregistry 13715 &
> set CLASSPATH=$OLDCLASSPATH
That's OK.
> jmeter.properties diff on the controller node
> ---------------------------------------------
> $ diff -U1 jmeter.properties jmeter.properties.new
> --- jmeter.properties 2005-09-23 00:10:21.000000000 +0100
> +++ jmeter.properties.new 2005-11-21 15:26:16.000000000 +0000
> @@ -87,3 +87,3 @@
> # Remote Hosts - comma delimited
> -remote_hosts=127.0.0.1
> +remote_hosts=127.0.0.1,bert.dev.uk.betfair
> #remote_hosts:localhost:1099,localhost:2010
> @@ -91,3 +91,3 @@
> # RMI port to be used by the server
> -#server_port=1099
> +server_port=13715
> @@ -358,3 +358,3 @@
> # Change default port used by server (need to start rmiregistry with
> same port)
> -#server.rmi.port=1099
> +server.rmi.port=13715
I think that should be done on the client node.
It won't harm to set them both to 13715 on both client and controller.
> tcpdump showing connection on 1099/tcp with above configs
> ---------------------------------------------------------
> 15:15:26.788354 mutare.32921 > bert.dev.uk.betfair.1099: S
> 3349072793:3349072793(0) win 5840 <mss 1460,sackOK,timestamp 615613839
> 0,nop,wscale 2> (DF)
>
> --
> Ollie Cook
> UNIX Scripter
> Information Systems
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: remote testing, different rmi port
Posted by Ollie Cook <ol...@betfair.com>.
On Mon, 2005-11-21 at 15:29 +0000, Ollie Cook wrote:
> Is server_port in jmeter.properties not the correct file to be using?
> I've tried setting server.rmi.port to 13715 as well, to no avail.
For the benefit of the mailing list archive, the port can be specified
on a per-host basis on the remote_hosts line in jmeter.properties.
e.g.: remote_hosts=127.0.0.1,bert.dev.uk.betfair:13715
If I'd have had my eyes open, I'd have seen that in the sample
configuration file, albeit without explanation.
Apologies for the list noise.
Ollie
--
Ollie Cook
UNIX Scripter
Information Systems
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org