If this is the case, it should show up in the JMeter server log,
because JMeter won't be able to start the RMI server on the default
port.

On 29/05/2009, drubix <[email protected]> wrote:
>
>  Perhaps your friend is running another process that uses RMI and is already
>  using the default port.  Maybe get your friend to start JMeter listening on
>  another port using the -Dserver_port switch?  Then just specify the remote
>  port along with your friend's IP in jmeter.properties like ip:port (e.g.
>  192.168.0.100:2020 for port 2020).
>
>
>
>  Chintan Kachhi wrote:
>  >
>  >
>  > I am using JMeter version 2.3.3. I have followed the instructions  in:
>  > 
> http://jakarta.apache.org/jmeter/usermanual/jmeter_distributed_testing_step_by_step.pdf
>  >
>  > My system is the master system, and my friend's system is the slave
>  > system. I am trying to do remote testing by running JMeter: Run -> Remote
>  > Start -> his I.P. address. However this is not working, and looking at the
>  > log, I am getting the following error messages:
>  >
>  >
>  > 2009/05/28 14:46:43 ERROR - jmeter.gui.action.RemoteStart: Failed to
>  > initialise remote engine java.rmi.NoSuchObjectException: no such object in
>  > table
>  >     at
>  > sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown
>  > Source)
>  >     at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
>  >     at sun.rmi.server.UnicastRef.invoke(Unknown Source)
>  >     at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
>  >     at java.rmi.Naming.lookup(Unknown Source)
>  >     at
>  > 
> org.apache.jmeter.engine.ClientJMeterEngine.getEngine(ClientJMeterEngine.java:51)
>  >     at
>  > 
> org.apache.jmeter.engine.ClientJMeterEngine.<init>(ClientJMeterEngine.java:64)
>  >     at
>  > org.apache.jmeter.gui.action.RemoteStart.doRemoteInit(RemoteStart.java:163)
>  >     at
>  > org.apache.jmeter.gui.action.RemoteStart.doAction(RemoteStart.java:74)
>  >     at
>  > 
> org.apache.jmeter.gui.action.ActionRouter.performAction(ActionRouter.java:80)
>  >     at
>  > org.apache.jmeter.gui.action.ActionRouter.access$000(ActionRouter.java:42)
>  >     at
>  > org.apache.jmeter.gui.action.ActionRouter$1.run(ActionRouter.java:59)
>  >     at java.awt.event.InvocationEvent.dispatch(Unknown Source)
>  >     at java.awt.EventQueue.dispatchEvent(Unknown Source)
>  >     at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
>  >     at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
>  >     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
>  >     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
>  >     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
>  >     at java.awt.EventDispatchThread.run(Unknown Source)
>  >
>  >
>  > I hope I am doing it correctly. According to the documentation, he only
>  > has his JMeter server running ( not the JMeter running), and I only have
>  > my JMeter running ( and not the JMeter server running, even though running
>  > both in both the systems also did not make any difference). We both have
>  > the same JMeter version 2.3.3 running with the same JDK version 1.5. Is
>  > there something else that needs to be edited? The only change I made in
>  > the jmeter.properties file was to add his ip address under the
>  > remote_hosts property.
>  >
>  > Thanks,
>  >
>  > Chintan
>  >
>  >
>  > _________________________________________________________________
>  > Drag n’ drop—Get easy photo sharing with Windows Live™ Photos.
>  >
>  > http://www.microsoft.com/india/windows/windowslive/photos.aspx
>  >
>
>
> --
>  View this message in context: 
> http://www.nabble.com/Unable-to-do-remote-testing-tp23770605p23771911.html
>  Sent from the JMeter - User mailing list archive at Nabble.com.
>
>
>  ---------------------------------------------------------------------
>  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]

Reply via email to