Steve,
I have just managed to get this working with the following setup:
1. Remote JMeter box is running Mac OS X 10.2.2 and Java 1.4.1_01. I have
made two scripts (I haven't bothered tidying it up as I do not actually
intend running it on this machine) in my jmeter/bin directory thus (they are
the same but for the last line):
rmireg:
#! /bin/sh
export JMETER_HOME=`dirname $0`/..
export
CLASSPATH=$CLASSPATH:$JMETER_HOME/lib/ext/ApacheJMeter_core.jar:$JMETER_HOME
/lib/jorphan.jar:$JMETER_HOME/lib/logkit-1.0.1.jar
rmiregistry
jmserv:
#! /bin/sh
export JMETER_HOME=`dirname $0`/..
export
CLASSPATH=$CLASSPATH:$JMETER_HOME/lib/ext/ApacheJMeter_core.jar:$JMETER_HOME
/lib/jorphan.jar:$JMETER_HOME/lib/logkit-1.0.1.jar
`dirname $0`/jmeter -s
I execute ./rmireg, wait a brief period then execute ./jmserv (running from
two terminal windows in case any interesting messages are sent to
stdout/err).
2. Master machine is a Win2k box. Only change was to add the IP address of
remote machine to jmeter.properties.
3. The app server is a RedHat box off somewhere in the distance.
Everything seems to work as advertised.
One thing to be careful about is that there is not a firewall interfering.
I opened up TCP port 1099 on my Mac, but this did not seem to be enough -
killing the firewall altogether did however get things ticking along nicely.
I will need to determine the exact firewall properties as in reality I will
be running my remote machine at a location where killing the firewall is not
an option - I'll post details when I work this out.
Good luck,
Scott
--
Scott Eade
Backstage Technologies Pty. Ltd.
http://www.backstagetech.com.au
.Mac Chat/AIM: seade at mac dot com
On 19/12/2002 5:54 AM, "Lawrence, Steve" <[EMAIL PROTECTED]> wrote:
>> I had trouble getting this working and discovered that there's an error in
>> the web page documenation regarding the classpath.
>
> Oh dear..
>
>> The last item, "logkit-1.0.1" should have a ".jar" appended to it. Again,
>> the docs say they're all jars, so a person could figure it out, but I
> didn't
>> and spent four hours in a lesson about how to pay attention. I had just
>> copied and pasted the paths and missed that little detail.
>
> I didn't catch it either, I've been following the instructions pretty much
> to the letter and wouldn't have the knowledge to know that it should have a
> .jar on the end.
>
> So.. I still can't get this working. I'm still getting 'bad call to remote
> host', and jmeter.log is still saying :
>
> 12/18/2002 1:32:24 PM ERROR - jmeter.engine: rmiregistry needs to be running
> to start JMeter in server mode java.rmi.UnmarshalException: Error
> unmarshaling return header; nested exception is:
> java.net.SocketException: Connection reset
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:203)
>
>
> From: Mike Stover
>> rmiregistry has to be running first, and then start the jmeter
> server(jmeter -s).
>
> This I have done. In order I :
>
> 1) check my CLASSPATH
> #echo $CLASSPATH
> /home/lawreste/jakarta-jmeter/lib/ext/ApacheJMeter_core.jar:/home/lawreste/j
> akarta-jmeter/lib/jorphan.jar:/home/lawreste/jakarta-jmeter/lib/logkit-1.0.1
> .jar:/usr/java/j2sdk1.4.1_01
>
> 2)rmiregistry &
> 3)./jmeter -s &
>
> 4)head jmeter.log
> 5)*panic*
>
>> The system classpath has to include the appropriate jars for rmiregistry,
> not for JMeter.
>
> This confuses me. If I understand correctly, rmiregistry is attempting to
> 'register' various calls which are used by Jmeter to do remote running. So,
> if I have my Jmeter jar's in my CLASSPATH, rmiregister should pick them up,
> register them, and um.. make them available when my NT contacts my RedHat on
> port 1099.
>
> Does rmiregistry need something that's not with Jmeter? I've putzed around
> with my CLASSPATH - tacked on my JAVA_HOME directory, in case there's
> something there it needs.
>
>
>> Also note that rmiregistry can sometimes leave processes hanging, even when
> it looks shut down.
>> I have in the past found that rebooting my NT machine to be the only sure
> way ofclearing such things
>> out.
>
> Well, I'm running this on a Redhat box, so I'm pretty sure if I've killed
> the process it's dead. Just to make sure I've killed the process, checked my
> netstat and confirmed that the box is no longer listening on 1099.
>
> In a fit of pique I also rebooted the box, ran the commands above and still
> get the same Jmeter error.
>
>> If JMeter says rmiregistry is not running, it's pretty good bet it's right.
>
> I'm 100 percent sure that rmiregistry is running. I see it in my process
> list, I see it listening on 1099, I'm almost certain that it's not picking
> up the Jmeter jars / classes / things I don't know about, though.
>
> Can anyone post a sample CLASSPATH / JAVA_HOME, I can look at to see if I've
> made a classic booboo?
>
> Thanks muchly,
> Steve.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
