Possible solution:
I was able to get Remote JMeter to work after moving the JMeter out of
"Program Files" directory. This was discovered when my boss stepped in to
help and I ended up installing JMeter in c:\
I believe JMeter has a problem resolving its own classpaths when
directory path has spaces in it?
Proof:
I have two JMeter trees on the same box one in
C:\Program Files\jakarta-jmeter
and one in c:\jakarta-jmeter
Start cmd shell in C:\j2sdk1.4.0_03\bin
set JMHOME=C:\"Program Files"\jakarta-jmeter
set
CLASSPATH=%JMHOME%\lib\ext\ApacheJMeter_core.jar;%JMHOME%\lib\jorphan.jar;%JMHOME%\lib\logkit-1.0.1.jar
start rmiregistry
In a new cmd shell
Starting C:\Program Files\jakarta-jmeter\bin\jmeter -s produces
the "..rmiregistry needs to be started error..."
Shutdown jmeter -s and exit cmd shell
In another new cmd shell start the version outside "Program Files"
Starting c:\jakarta-jmeter\bin\jmeter -s SUCCESS!
Note: I set the JMHOME every way I could think of without success.
That is, initially without quotes, then using the short name
progra~1, then quoting it. I'm guessing this is because rmiregistry is
picking these paths up fine and JMeter is attempting to construct its own
and failing when spaces are in the classpath.
For all those who had successes can you verify that you did not have
JMeter installed in "Program Files" or a directory path which contained
spaces? Or, point out a flaw in my theory...
Thanks For The FeedBack!
I doubt I would have stuck with this without it.
|------------------------------|
| Ryan Russo |
| University at Albany |
| Computing |
| Technical Services Web Team |
|------------------------------|
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
