GoogleCloudPlatform / solutions-google-compute-engine-cluster-for-jmeter

Apache License 2.0
21 stars 16 forks source link

SSH tunnels are not working with newest version of Jmeter (2.13). #1

Open drptbl opened 9 years ago

drptbl commented 9 years ago

SSH tunnels are working fine with Jmeter 2.9.

When changing setup to JDK 1.7 together with Jmeter 2.13 (same setup, only JDK and Jmeter changes) getting errors while trying to start a test.

Explanation:

  1. Everything is set-up, going into script dir and running:
./jmeter_cluster.py start
  1. Machines are getting up and everything works (no errors in console)
  2. Time to run my test script. Running this command:
./jmeter_cluster.py client -n -t /root/test.jmx -l /root/test.jtl -R 127.0.0.1:24000,127.0.0.1:24001,127.0.0.1:24002
  1. Getting these errors after running previous command:
Creating summariser <summary>
Created the tree successfully using /root/test.jmx
Configuring remote engine: 127.0.0.1:24000
error during JRMP connection establishment; nested exception is: 
    java.io.EOFException
Failed to configure 127.0.0.1:24000
Configuring remote engine: 127.0.0.1:24001
error during JRMP connection establishment; nested exception is: 
    java.io.EOFException
Failed to configure 127.0.0.1:24001
Configuring remote engine: 127.0.0.1:24002
error during JRMP connection establishment; nested exception is: 
    java.io.EOFException
Failed to configure 127.0.0.1:24002
Stopping remote engines
Remote engines have been stopped
Error in NonGUIDriver java.lang.RuntimeException: Following remote engines could not be configured:[127.0.0.1:24000, 127.0.0.1:24001, 127.0.0.1:24002]
  1. In the meanwhile in console when I ran "start" command, I'm getting these errors:
channel 4: open failed: connect failed: Connection refused
channel 4: open failed: connect failed: Connection refused
channel 4: open failed: connect failed: Connection refused

I mention again - Jmeter 2.9 works fine, Jmeter 2.13 doesn't. Any way to fix this?

caoimhek7 commented 5 years ago

Hi, I am getting the same issue, I know this was years ago but any chance you resolved it? Caoimhe