On 05/03/2008, Tom Fernandes <[EMAIL PROTECTED]> wrote:
> Hi,
>
>
>  On Wednesday, 5. March 2008, sebb wrote:
>  > On 05/03/2008, Tom Fernandes <[EMAIL PROTECTED]> wrote:
>  > > Hello,
>  > >
>  > >  I'm trying to run jmeter remote. Setup as follows:
>  > >
>  > >  run jmeter-server on the remote machine (as it looks it binds default to
>  > > port 1099)
>  > >
>  > >  on the node have one line
>  > >
>  > >  remote_hosts=127.0.0.1:1099
>  > >
>  > >  ssh port forwarding from 1099 of 127.0.0.1 on local machine to 127.0.0.1
>  > > on remote machine. The forwarding works (tested via portsniffing on the
>  > > remote machine).
>  >
>  > RMI requires that the client can find the server, and the server can
>  > find the client.
>  >
>  > The client sends a message to the server; this includes its return address.
>  > The server has to be able to contact the client to return any sample data.
>  >
>  > If either the client or the server thinks its ip address is a "local"
>  > address, then the communication will fail to work fully.
>  >
>  > If possible, please try using client server mode without ssh forwarding
>  > first.
>
>
> Hmm - sounds tricky. Node is in the office (internal IP behind a router) -
>  remote server is in the data center (in the same subnet where the server we
>  want to test is). What would you suggest? I dislike the idea of having the
>  jmeter server run on a public port and would rather not have portforwarding
>  from the office router to the jmeter node.

I just meant to try the client-server set up between the current
client and another node that is accessible without ssh. Ideally also
use another client and the server without ssh.

That should show if the individual nodes are working OK, and you can
then worry about adding the ssh tunneling.

>  But if necessary we'll open up things a bit. What what the configuration be
>  like. Is it possible to either bind jmeter-server onto the external interface
>  or do the portforwarding into the lan or would we have to do both?
>

Sorry, no idea. That's really an RMI/Networks issue; I have little
knowledge of that.

One alternative might be use JMeter in non-GUI mode on the server via
ssh from the client.

If you are only running one server that would be equivalent and would
reduce the network traffic during the test.

>
>  regards,
>
>
>  Tom
>
>
>  >
>  > >  start up jmeter, load my test plan choose Run -> Remote Start ->
>  > >  localhost:1099
>  > >
>  > >  On the local machine I get a pop up window with the title: Error
>  > > initializing remote server. Nothing gets logged into the logfile of the
>  > > remote host once I start the client. The clients logfile is attached to
>  > > the end of this mail. It starts at the time the error occurs.
>  > >
>  > >  I also tried using a different port on the server/node - didn't work
>  > > either.
>  > >
>  > >  Am I missing anything?
>  > >
>  > >
>  > >  Thanks,
>  > >
>  > >
>  > >  Tom
>  > >
>  > >
>  > >  -----------------------8<------------------------------------
>  > >
>  > >  2008/03/05 15:11:31 ERROR - jmeter.gui.action.RemoteStart: Failed to
>  > >  initialise remote engine java.rmi.NotBoundException: JMeterEngine
>  > >         at sun.rmi.registry.RegistryImpl.lookup(RegistryImpl.java:106)
>  > >         at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
>  > >         at
>  > >  sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:386)
>  > >         at
>  > > sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:250) at
>  > > sun.rmi.transport.Transport$1.run(Transport.java:159) at
>  > > java.security.AccessController.doPrivileged(Native Method) at
>  > > sun.rmi.transport.Transport.serviceCall(Transport.java:155) at
>  > >  sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
>  > >         at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0
>  > >  (TCPTransport.java:790)
>  > >         at
>  > >
>  > > sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.jav
>  > >a:649) at
>  > >
>  > > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor
>  > >.java:885) at
>  > >
>  > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.jav
>  > >a:907) at java.lang.Thread.run(Thread.java:619)
>  > >         at
>  > >
>  > > sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemo
>  > >teCall.java:255) at
>  > >
>  > > sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)
>  > > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:359) at
>  > > sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source) at
>  > > java.rmi.Naming.lookup(Naming.java:84)
>  > >         at
>  > >
>  > > org.apache.jmeter.engine.ClientJMeterEngine.getEngine(ClientJMeterEngine.
>  > >java:52) at
>  > >
>  > > org.apache.jmeter.engine.ClientJMeterEngine.<init>(ClientJMeterEngine.jav
>  > >a:56) at
>  > >
>  > > org.apache.jmeter.gui.action.RemoteStart.doRemoteInit(RemoteStart.java:16
>
> > >0) at
>
> > >  org.apache.jmeter.gui.action.RemoteStart.doAction(RemoteStart.java:73)
>  > >         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(InvocationEvent.java:209) at
>  > > java.awt.EventQueue.dispatchEvent(EventQueue.java:597) at
>  > >
>  > > java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.j
>  > >ava:273) at
>  > >
>  > > java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java
>  > >:183) at
>  > >
>  > > java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.j
>  > >ava:173) at
>  > >  java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
>  > >         at
>  > >  java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
>  > >         at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
>  > >
>  > >
>  > > ------------------------------------------------------------------------>
>  > >8-------------
>  > >
>  > >  ---------------------------------------------------------------------
>  > >  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]

Reply via email to