Looks like it is not starting the registry. Try changing to the JMeter bin directory before running jmeter-server.
If this does not start the registry, then start it separately first. S. On 5/3/05, Douglas Doyer <[EMAIL PROTECTED]> wrote: > Hi, > As mentioned in the email, the client and the server are on the same > machine (with an aim of trying out JMETER). Thus, there are surely no > PING problems > > Indeed, I open a DOS command window, I move in the BIN directory and I try to > start the Jmeter Server by the jmeter-server.bat script. At this moment, I > already have an error in the file jmeter.log: > > Microsoft Windows XP [version 5.1.2600] > (C) Copyright 1985-2001 Microsoft Corp. > > C:\Documents and Settings\ddo>C:\jmeter\bin\jmeter-server.bat > Changing to JMeter home directory > Found ApacheJMeter_core.jar > [Full GC 2477K->554K(249088K), 0.0233500 secs] > > C:\Documents and Settings\ddo> > > 2005/05/03 08:06:36 INFO - jmeter.JMeter: Version 2.0.3 > 2005/05/03 08:06:36 INFO - jmeter.JMeter: java.version=1.4.2_07 > 2005/05/03 08:06:36 INFO - jmeter.JMeter: Copyright (c) 1998-2005 The Apache > Software Foundation > 2005/05/03 08:06:37 INFO - jmeter.engine.RemoteJMeterEngineImpl: Starting > backing engine > 2005/05/03 08:06:37 ERROR - jmeter.engine.RemoteJMeterEngineImpl: rmiregistry > needs to be running to start JMeter in server mode > java.rmi.ServerException: Server RemoteException; nested exception is: > java.rmi.UnmarshalException: error unmarshalling arguments; nested > exception is: > java.lang.ClassNotFoundException: > org.apache.jmeter.engine.RemoteJMeterEngineImpl_Stub > 2005/05/03 08:06:37 ERROR - jmeter.JMeter: Giving up, as server failed with: > java.rmi.RemoteException: Cannot start. See server log file. > at > org.apache.jmeter.engine.RemoteJMeterEngineImpl.<init>(RemoteJMeterEngineImpl.java:56) > at org.apache.jmeter.JMeter.startServer(JMeter.java:483) > at org.apache.jmeter.JMeter.start(JMeter.java:289) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > 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 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. > > I assume you are running jmeter-server on one node and jmeter on the > client node? > And can you ping the server node from the client node? And vice versa? > > Also, you should really be in the JMeter bin directory when launching JMeter. > The command files try to do this, but it would not harm to start from there. > > S. > On 5/3/05, Douglas Doyer <[EMAIL PROTECTED]> wrote: > > Hi, > > However, this is what I did: > > > > JAVA_HOME=C:\progra~1\j2sdk142 > > JMETER_HOME=c:\jmeter > > CLASSPATH=C:\jmeter\lib\ext\ApacheJMeter_core.jar;C:\jmeter\lib\jorphan.jar;C:\jmeter\lib\logkit-1.2.jar > > > > There is not space in the name of the directory given. The fact of > > installing JAVA SDK in c:\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/3/05, Douglas Doyer <[EMAIL PROTECTED]> wrote: > > > Hi, > > > The client and the server are on the same machine and using the > > > same binary file of JMETER. I am certain that it should not miss a lot of > > > thing. > > > > > > 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 & 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 in < Remote Testing >. In my experimentation, I > > > > tried to use the client and the server on the same Windows XP machine. > > > > > > > > - Sun J2SE JSK 1.4.2 (C:\Program Files\j2sdk142) > > > > > > > > - JMeter 2.03 (C:\jmeter) > > > > > > > > - Windows XP SP2 with no Firewall activated > > > > > > > > Here my system environments variables: > > > > > > > > JAVA_HOME=C:\progra~1\j2sdk142 > > > > > > > > JMETER_HOME=c:\jmeter > > > > > > > > CLASSPATH=C:\jmeter\lib\ext\ApacheJMeter_core.jar;C:\jmeter\lib\jorphan. > > > > jar;C:\jmeter\lib\logkit-1.2.jar > > > > > > > > I tested the described procedure at > > > > http://jakarta.apache.org/jmeter/usermanual/remote-test.html > > > > <http://jakarta.apache.org/jmeter/usermanual/remote-test.html> , but > > > > without success. Here in detail the steps that I made: > > > > > > > > 1. Execute the step 1 described in the procedure in a new DOS Windows > > > > (cmd.exe) > > > > > > > > Microsoft Windows XP [version 5.1.2600] > > > > > > > > (C) Copyright 1985-2001 Microsoft Corp. > > > > > > > > C:\Documents and Settings\ddo>C:\jmeter\bin\jmeter-server.bat > > > > > > > > Changing to JMeter home directory > > > > > > > > Found ApacheJMeter_core.jar > > > > > > > > [Full GC 2477K->554K(249088K), 0.0231871 secs] > > > > > > > > C:\Documents and Settings\ddo> > > > > > > > > Note: At this moment, another Windows appear (rmiregistry) with this > > > > message "security properties not found. Using defaults.". > > > > > > > > Note 2: Here the result of the jmeter.log log file > > > > > > > > 2005/04/29 09:52:08 INFO - jmeter.JMeter: Version 2.0.3 > > > > > > > > 2005/04/29 09:52:08 INFO - jmeter.JMeter: java.version=1.4.2_07 > > > > > > > > 2005/04/29 09:52:08 INFO - jmeter.JMeter: Copyright (c) 1998-2005 The > > > > Apache Software Foundation > > > > > > > > 2005/04/29 09:52:08 INFO - jmeter.engine.RemoteJMeterEngineImpl: > > > > Starting backing engine > > > > > > > > 2005/04/29 09:52:08 ERROR - jmeter.engine.RemoteJMeterEngineImpl: > > > > rmiregistry needs to be running to start JMeter in server mode > > > > > > > > java.rmi.ServerException: Server RemoteException; nested > > > > exception is: > > > > > > > > java.rmi.UnmarshalException: error unmarshalling arguments; > > > > nested exception is: > > > > > > > > java.lang.ClassNotFoundException: > > > > org.apache.jmeter.engine.RemoteJMeterEngineImpl_Stub > > > > > > > > 2005/04/29 09:52:08 ERROR - jmeter.JMeter: Giving up, as server failed > > > > with: java.rmi.RemoteException: Cannot start. See server log file. > > > > > > > > at > > > > org.apache.jmeter.engine.RemoteJMeterEngineImpl.<init>(RemoteJMeterEngin > > > > eImpl.java:56) > > > > > > > > at org.apache.jmeter.JMeter.startServer(JMeter.java:483) > > > > > > > > at org.apache.jmeter.JMeter.start(JMeter.java:289) > > > > > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > > > > Method) > > > > > > > > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown > > > > Source) > > > > > > > > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown > > > > Source) > > > > > > > > at java.lang.reflect.Method.invoke(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 > > > > carry out the same experimentation on Linux RedHat AS 3.0 and still have > > > > an error when try to start the server. What do I miss? Is this possible > > > > to help me? > > > > > > > > Thanks. > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
