I wouldn't be surprised if the firewall was at least partially
responsible... I allowed 1099 from the controller to the jmeter-server
units, but I can't find any info on any other ports that may be
necessary, and 127.0.0.1 is failing on the master. I can ping the two
"slaves", too.
2006/06/28 17:
very well.
Thanks for you help
BYe
-Message d'origine-
De : sebb [mailto:[EMAIL PROTECTED]
Envoyé : 3 mai 2005 08:16
À : Douglas Doyer
Cc : JMeter Users List
Objet : Re: Bad Call to remote host
Looks like it is not starting the registry.
Try changing to the JMeter bin directory b
rce)
>at java.lang.reflect.Method.invoke(Unknown Source)
>at org.apache.jmeter.NewDriver.main(NewDriver.java:172)
>
> Bye
>
>
> -Message d'origine-
> De: sebb [mailto:[EMAIL PROTECTED]
> Envoyé: 3 mai 2005 08:04
> À: Douglas Doyer
> Cc: JMeter Users
Message d'origine-
De : sebb [mailto:[EMAIL PROTECTED]
Envoyé : 3 mai 2005 08:04
À : Douglas Doyer
Cc : JMeter Users List
Objet : Re: Bad Call to remote host
I don't think it matters having spaces in the Java directory.
However JMeter doesn't like them when using client-se
d'origine-
De : sebb [mailto:[EMAIL PROTECTED]
Envoyé : 3 mai 2005 08:04
À : Douglas Doyer
Cc : JMeter Users List
Objet : Re: Bad Call to remote host
I don't think it matters having spaces in the Java directory.
However JMeter doesn't like them when using client-server mode.
ogra~1
> could cause problems?
>
> Thanks.
>
> -Message d'origine-
> De: sebb [mailto:[EMAIL PROTECTED]
> Envoyé: 3 mai 2005 07:53
> À: JMeter Users List
> Objet: Re: Bad Call to remote host
>
> Make sure there are no spaces in the directory names.
>
:\program File and giving the DOS path c:\progra~1 could cause
problems?
Thanks.
-Message d'origine-
De : sebb [mailto:[EMAIL PROTECTED]
Envoyé : 3 mai 2005 07:53
À : JMeter Users List
Objet : Re: Bad Call to remote host
Make sure there are no spaces in the directory names.
S.
On 5
ng.
>
> Thanks.
>
> -Message d'origine-
> De: Shabana Shabana [mailto:[EMAIL PROTECTED]
> Envoyé: 3 mai 2005 02:12
> À: JMeter Users List
> Objet: Re: Bad Call to remote host
>
> Hi,
>
> Make sure that jmeter & jdk versions are same on client
Objet : Re: Bad Call to remote host
Hi,
Make sure that jmeter & jdk versions are same on client & remote server .
It seems irrelevant but its required.
Regards,
Shabana
On 4/29/05, Douglas Doyer <[EMAIL PROTECTED]> wrote:
> Hi everyone,
>
> I try to use JMeter
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
> Source)
>
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
>
> at java.lang
Unknown Source)
at org.apache.jmeter.NewDriver.main(NewDriver.java:172)
Well, if I try to continue step 2 and 3, I receives the following error
in the Jmeter Client : "Bad Call to remote host".
If I try to do it manually, I obtain the same result. I also tried to
ca
g the following error message from the controller
machine when trying to run the distrubted test:
"Bad call to remote host"
I get the error message from the GUI under these circumstances:
- when I Run > Remote Start > 127.0.0.1
- When I Run > REmote Start All (I get several pop-ups wi
r 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 &#
solve each others IPs by name.
Don't use different JVMs.
On *nix hosts, remove the servers name alias to
127.0.0.1.
--- Michael Kandall <[EMAIL PROTECTED]> wrote:
>
> I am trying to get started with remote measurement.
>
> When running jmeter in remote mode, the client
(BI am trying to get started with remote measurement.
(B
(BWhen running jmeter in remote mode, the client says "Bad call to remote
(Bhost".
(BErrors in the server-side log file are below.
(B
(Bjmeter-server is not registering with rmiregistry?
(B
(B. $JMETER_HOME/bin/jmeter-server is exe
erver process on the solaris box, and what
errors are appearing in the jmeter.log files of both the client and server machines.
-Mike
On 28 Aug 2003 at 13:00, Duncan Frostick wrote:
Ok, I've opened port 1099 (rmiregistry) on the server and now I don't get the Bad
call to remote host err
errors are appearing in the jmeter.log files of both the client and server machines.
>
> -Mike
>
> On 28 Aug 2003 at 13:00, Duncan Frostick wrote:
>
> > Ok, I've opened port 1099 (rmiregistry) on the server and now I don't get the Bad
> > call to remote hos
xactly how you start the jmeter server process on the solaris box,
> and what
> errors are appearing in the jmeter.log files of both the client and server machines.
>
> -Mike
>
> On 28 Aug 2003 at 13:00, Duncan Frostick wrote:
>
> > Ok, I've opened port 1099 (rmi
rver and now I don't get the Bad
> call to remote host error, but now the tests simply wont start. After I click remote
> start on the server I want, the green indicator is not turned on and no results are
> returned.
>
> What could possibly be going wrong, the docs say just
On the server, after you started the RMI service, did you start jmeter
with the -s option?
Regards,
Vishal.
Duncan Frostick wrote:
Ok, I've opened port 1099 (rmiregistry) on the server and now I don't get the Bad
call to remote host error, but now the tests simply wont start. Aft
Ok, I've opened port 1099 (rmiregistry) on the server and now I don't get the Bad
call to remote host error, but now the tests simply wont start. After I click remote
start on the server I want, the green indicator is not turned on and no results are
returned.
What could possibly be g
box and a 1.9.1 client on a Win98 and
a Win2k box. I'm trying to control the server from either the Win98 or Win2k box
but everytime I try to run a test plan remotely on either (using Remote
Start>172.26.0.12) I get a 'Bad call to remote host' box pop up twice and
nothing happen. I
I have a JMeter 1.9.1 server on a Solaris box and a 1.9.1 client on a Win98 and
a Win2k box. I'm trying to control the server from either the Win98 or Win2k box
but everytime I try to run a test plan remotely on either (using Remote
Start>172.26.0.12) I get a 'Bad call to remote hos
es,
then I defined "HTTP request" wherein I entered http request name, server
IP address/port #(80) and path.
Then from main menu I chosed "Remote start" which now shows my website ip
address, but immediately after clicking this, return error as "Bad call to
remote host"
10:40 AM
To: [EMAIL PROTECTED]
Subject: "Bad call to remote host" in distributed testing
Hi,
I am trying to do distributed testing. I think that I followed all the steps
described in manual. But, when I pressed a server button in remote-start
menu, they always showed a message - &q
Hi,
I am trying to do distributed testing. I think that I followed all the
steps
described in manual. But, when I pressed a server button in remote-start
menu, they always showed a message - "Bac call to remote host".
Although I searched previous mail archieve, I can't find any clues.
Please,
26 matches
Mail list logo
