On 10/02/2010, Andreas Niemeyer <[email protected]> wrote: > Hi, > > I tried to download the patched class from the wiki page but the download > is broken. > > I guess it shouldn't be enough to enable only one specific port since more > objects are created during a test - I noticed that for a simple http load > test I did 2 ports were opened - checked via netstat - and a fixed single > port would probably be a bottleneck for the test. > > Is it planned to implement such a config option to enable a port range for > the RMI communication?
Patches (via Bugzilla) are always welcome... > I think it would be quite useful because of the chance to drive tests with > defined firewall rules and across different subnets. You can also use rsh or similar to run non-GUI JMeter instances on as many remote servers as you want, and then combine the results files. This will use far fewer resources as the responses don't have to be sent during the test run (even with statistical sampling, this can eventually become a bottleneck). > > Regards, > Andreas > > > Andreas Niemeyer schrieb: > > > > Hi, > > > > I need to setup a jmeter remote server and have the problem that the RMI > ports are opened dynamically instead of set them static. > > > > I read the Wiki about RMI and firewall issues and the comments date of it. > Does there in the meanwhile a simple config property exist to avoid writing > new classes or to exchange code pieces? > > > > Thank you for some hints, > > Andreas > > > > > > > http://wiki.apache.org/jakarta-jmeter/JMeterRemoteTestingEnhancements > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [email protected] > For additional commands, e-mail: > [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
