Page History

...

All in all it is nothing like the issue I originally imagined it to be. – ScottEade 2003-01-16

a modified version

re remote testing and firewall issues, just modified jmeter source based on v2.1.1. with the modification, a new property 'server.service.port' could be used for the jmeter service port (pls note this is different from the rmi registry port which could also be configured by 'server.rmi.port') in jmeter.properties. current jmeter release uses a random port number which may cause some trouble for sysadmin to adjust firewall rules (especially if you sysadmin is very much concerned about any potential security issues). so you could give jmeter a static port number for the service and let sysadmin know the port as well.

• Wiki Markup

  if you only need binary (working copy), download ApacheJMeter_core.jar \[http://wiki.apache.org/jakarta-jmeter-data/attachments/JMeterRemoteTestingEnhancements/attachments/ApacheJMeter_core.jar\] which is recompiled with my change; and as an option, feel free to download new jmeter.properties \[http://wiki.apache.org/jakarta-jmeter-data/attachments/JMeterRemoteTestingEnhancements/attachments/jmeter.properties\]. \\

• Wiki Markup

  for source code, pls download two patches, one for src/core/org/apache/jmeter/engine/RemoteJMeterEngineImpl.java \[http://wiki.apache.org/jakarta-jmeter-data/attachments/JMeterRemoteTestingEnhancements/attachments/RemoteJMeterEngineImpl.java.patch.txt\] and the other for bin/jmeter.properties \[http://wiki.apache.org/jakarta-jmeter-data/attachments/JMeterRemoteTestingEnhancements/attachments/jmeter.properties.patch.txt\]. simply apply them and job done. \\

(I have been looking for any chance contribute that modification back to main development tree, so feel free to use it if it could be included in a future release)

...