topic Re: jmeter through ssh tunneling in Operating System - Linux

jmeter through ssh tunneling

JM9 — Thu, 05 Apr 2007 09:29:58 GMT

I am trying to use hpjmeter console on my PC tunneling through ssh connection. I can see the jvm instance but when I try to connect to it all I see is a message "Waiting for JVM Agent communication" and then nothing.

I can use the console on the server with Xserver but this is very slow. Has anyone done this before?

Re: jmeter through ssh tunneling

Steven E. Protter — Thu, 05 Apr 2007 09:34:29 GMT

shalom,

Consider checking tcpdump, but I think this software is not compatible with being tunnelled like that.

Either that or the tunnelling is slowing down your already very slow xserver.

SEP

Re: jmeter through ssh tunneling

JM9 — Thu, 05 Apr 2007 09:59:34 GMT

Shalom!

The documentation refers to the fact that this tool can tunnel through ssh. The agent listens on a single port 9505. when the ssh is connected with -L9505:localhost:9505 I can see the tunnel established and it is confirmed by the fact that I can see the JVM instance in the console.

Re: jmeter through ssh tunneling

JZ2 — Wed, 11 Apr 2007 14:30:21 GMT

At the moment, HPjmeter doesn't make it easy to send the session data through the tunnel. When you open a session with a particular JVM, the console opens a socket on a new port for this communication.

With the current behavior of the console, I suggest that you consider running the console on the server. You can use vnc to forward the display to your pc. This results in better responsiveness than forwarding the X display directly.

Re: jmeter through ssh tunneling

JM9 — Wed, 11 Apr 2007 16:07:55 GMT

This is exactly what I am doing. Using ssh to forward X traffic to my PC but this is very^n slow.

Is there a bug open to fix this in some upcoming release? - Sunit

Re: jmeter through ssh tunneling

Univer_1 — Wed, 11 Apr 2007 22:39:04 GMT

Hi

Maybe a jre version problem I met before.

Some new version jre like jre-1_5_0_11 will hang on starting program.

Try use older jre like j2re-1_4_2_13.

Regards

Univer

Re: jmeter through ssh tunneling

JZ2 — Thu, 12 Apr 2007 09:00:55 GMT

Yes, remote X displays can be slow, depending on the network. It sounds like you are sending the X display over the network. I have seen much better response when running a vnc server on the same system as the console, and using a vnc client on the pc to view the display on the pc. Vnc tends to be more efficient than the X protocol over slow network links.

Yes, there is a task to improve how HPjmeter works in this situation, in a future release.

Re: jmeter through ssh tunneling

JM9 — Thu, 12 Apr 2007 09:09:45 GMT

Hi Univer,

Where should 1.4.2 be used? For console?

Sunit

Re: jmeter through ssh tunneling

Univer_1 — Fri, 13 Apr 2007 00:07:53 GMT

Yes, If you run the HPjmeter console on Windows systems, try to install a old jre (java runtime env).

regards

Univer

Re: jmeter through ssh tunneling

JZ2 — Fri, 13 Apr 2007 09:55:34 GMT

Univer,

I do not agree with your suggestion to run the console with an old version of Java. I run the console with 1.5.0_11 on a regular basis, and I have not experienced a problem like the one you described.

If you can reproduce this, please report it to HP. The best way to report an issue with HPjmeter is to use the form at http://www.hp.com/products1/unix/java/tools-support.html

Re: jmeter through ssh tunneling

JM9 — Fri, 13 Apr 2007 13:31:09 GMT

I tried the console wth different version sof Java and it did not help. In each case the message "Waiting for JVM Agent communication..." was displayed in the bottom status area for a few seconds and then went away. The JVM in the list of JVMs under nodeagent shows a icon that looks like an arrowhead with a red sqaure and Open Session with (bootstrap classname) (uptime...)

This is where things stop. Immediately after clicking on the JVM to connect I checked all the network sockets using netstat -an command and I could not see anything that was waiting to connect (nothing in SYN_SENT status that you would see if firewall was blocking the connection).
-Sunit