It turned out to be a software firewall rule preventing connections
from the primary address to the primary address. The other
required system software uses localhost for local connections,
so this had not been configured.
Btw, jmeter-server has a shell script error:
set CLASSPATH=...
which is not correct Bourne shell, does not do what the author expected.
I changed to
export CLASSPATH=...
Finally, sInce I am running behind a NAT firewall, I could not get the
RMI callbacks working, so I gave up on the remote execution feature.
I log into a machine outside the local NAT firewall, run in non-GUI mode
and import the resulting .jtl.
This worked for modest size .jtl, and could not seem to handle larger
requests.
Thanks,
> -----Original Message-----
> From: Drew Gulino [mailto:[EMAIL PROTECTED]
> Sent: Monday, November 17, 2003 11:48 PM
> To: JMeter Users List
> Subject: Re: jmeter-server: Bad call to remote host
>
>
> This is usually causes by mixing versions of Jmeter.
> The local and remote versions must be exactly the
> same. If you are not using the precompiled versions,
> compile on one machine and copy the 'binaries' to the
> remote machines.
>
> Check your /etc/hosts and make sure all machines can
> resolve each others IPs by name.
>
> Don't use different JVMs.
>
> On *nix hosts, remove the servers name alias to
> 127.0.0.1.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
