...
- Documentation of remote testing does not provide details of the ports that need to be open on a firewall
- Make remote testing easier and less error prone (provide shell scripts for rmiregistry or do not use RMI at all) – OliverRossmueller 2003-01-06
- The very first thing we should do is to update the jmeter-server scripts to set the classpath and start rmiregistry before starting jmeter. – ScottEade 2003-01-07
- Need a solution for tunneling RMI through a firewall (publicly available solutions exist). – ScottEade 2003-01-05
- Option to specify the port to be allocated by rmi. – ScottEade 2003-01-05 I just can't understand any situation where running JMeter remotely through a firewall is necessary or desirable. I can only think that people who insist on being able to do this have a fundamental misunderstanding of what a remote JMeter "server" is for - MikeStover)
- The ability to easily configure a set of remote testing hosts with varying parameters (number of threads to cater for testing hosts of varying capacity, counter values to handle things like ensuring user identifiers are unique across all test hosts) so that it is easier to initiate distributed testing from multiple remote hosts. – ScottEade 2003-01-07
- Ensure relevant items can be set using variables.
- Allow parameters to be specified on a per server basis (much like User Parameters), perhaps these would replace the User Defined Variables on the Test Plan element.
- Would want a checkbox to indicate which servers should be active for a test run (this would effectively define a single set of hosts, the members of which can be very easily updated).
- Could enter the address of the server here and eliminate the remote_hosts setting in jmeter.properties.
- Good thoughts - maybe a dialog box could provide a bunch of controls associated with starting a remote host - ie IP address, custom user-defined variables for that run, etc.
- Pass properties specified via jmeter -Jvariable=value through to remote servers. It took embarrassingly long for me to realize that if I pass -J properties on the command line and don't run with -r, the properties are set correctly for the local instance, but if I do pass -r, none of the remote servers see the property specified on the command line (they always get the default value). --ChrisNuzum 2006-10-18
...
RMI/Firewall issues
...