I have also had this working in the last couple of weeks - Win2k client and Mac OS X server. One important step was to disable the firewall on the Mac so that rmi could make it's connections. Other than this it worked fine for me (a way of configuring the port that will be used is on my list of potential enhancement requests).
Not sure about the out of memory references that are included in this thread - I assume you are allocating more of the available memory to the JVM used to tun JMeter by altering the java mx parameter on startup? Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au .Mac Chat/AIM: seade at mac dot com On 2/01/2003 6:24 AM, "Mike Stover" <[EMAIL PROTECTED]> wrote: > Yes, using 1.8. I don't know what all this talk of a pause in the script is > about. I start rmiregistry on one command line, and then go start jmeter in a > different one. I never use system-wide classpaths, as that's a recipe for > hard-to-debug problems. instead, I define a more local classpath in the > command line for rmiregistry, and then start rmiregistry. Admittedly, windows > doesn't localize such things as well as L/Unix, but, that's how I do it since > I'm more used to Unix in that regard. > > So, anyway, I just tried it again, and it worked perfectly my first try. For > rmiregistry, I opened a windows command prompt, set the CLASSPATH to the full > paths to jorphan.jar, logkitxxx.jar, and ApacheJMeter_core.jar. Then I > started rmiregistry. > > Then, I opened a new command prompt, and changed directory to jmeter's bin > dir, and started the server via "jmeter -s". > > then, I verified that my jmeter properties file included the "remote_hosts" > line uncommented (it did, with ip of 127.0.0.1 - I have only one computer, but > that shouldn't matter, it's still using RMI to communicate). > > Then, I started the JMeter gui, made a simple script,and ran it through the > remote ip. No problems. > > I am running Windows2000, jdk1.4.0, and latest JMeter code from CVS, which is > not different from 1.8 in this area. > > -Mike > > On 1 Jan 2003 at 14:10, [EMAIL PROTECTED] wrote: > >> To Mike, Steve, Barry: >> >> Hi Mike: >>> As far as problems with remote testing, all I can say is that, on >>> Windows2000, jdk1.4.0, it works for me. I won't deny that the classpath >>> issues can be tricky, however. >> Using JMeter 1.8? Would you mind sending your classpath and any related >> environment variables you have set? Maybe this will help Steve as well? >> Maybe I have conflict with other java paths already defined not >> related to JMeter. Just don't know java well enough to debug this on my >> own. >> >> Hi Steve: Thanks for the sympathy. ;) Other team members here are in >> dialog with Mercury Interactive if you can afford to go the >> consulting route. They're _very_ expensive (at least when you >> have no money). Estimate cost so far 50-70K: >> http://www.mercuryinteractive.com/ but, I believe they're doing much more >> than load testing. >> >> Hi Barry: >>> I have gotten JMeter working remotely. I run the GUI on a RedHat 8 box, >>> andhave 5 Windows 2000 boxes running as slaves. Getting the CLASSPATH >>> was a little tricky, and I put a "pause" in the .bat file... >> Using JMeter 1.8 and jre 1.4.0 ? Please confirm since there seems >> to be 3 big variances here, outside of classpath, which _could_ be >> causing the problem (OS,JMeter, and JRE versions). >> I did just try following the instructions first. Simply adding the 3 >> stated items to my classpath did not work. Did notice the missing .jar >> extension on logkit. Had a pause in my script as well. ;) >> >> Thanks for all the replies. Hoping to sort this out. >> Happy New Year All! >> -Ryan >> >> ---Start Whining [Read at own risk]:--- >> This is very frustrating since I've taken all the time to develop scripts >> for testing yet I am now stuck with having a limited load I can apply. I >> need to simulate 1000's of users on PC's which can probably only handle at >> best 10-20 threads. Just not practical to scale up my load testing without >> the remote testing portion working. >> >> BTW: I had similar "java out of memory problems" as stated on the list >> running 50 threads on a Win2k box with 512mg memory also encountered same >> issue on PIII 450 128mg running RH 8 (20 threads if my memory serves). The >> bulk testing machines I would have access to are only Win98 boxes with >> 64mg mem.... >> ----End Whining.---- >> >> >> >> >> >> >> -- >> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> >> > > > > -- > Michael Stover > [EMAIL PROTECTED] > Yahoo IM: mstover_ya > ICQ: 152975688 > AIM: mstover777 > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
