Apache Nifi ListFTP "Connection Refused" - apache-nifi

Can't connect to network drive
I have a instance of NiFi installed on Linux running Windows virtually. I am trying to use the ListFTP and FetchFTP processors to watch and pull files from a network shared drive with separate log in credentials from the user login for the VM instance. All of my attempts to connect to the network drive have failed so far with the same error (also visible in full log file below):
ListFTP[id=017010c5-a979-1da8-6ea7-d19acc59a3e7] Failed to perform listing on remote host due to Connection refused: connect: java.net.ConnectException: Connection refused: connect
I have tried to connect to the XXX.YYY.com hostname as well as ping the IP address and use that as a hostname. I can connect to the drive within the Windows instance with the same username and password credentials I am using in NiFi.
log file
2020-03-31 10:18:19,937 ERROR [Timer-Driven Process Thread-7] o.a.nifi.processors.standard.ListFTP ListFTP[id=017010c5-a979-1da8-6ea7-d19acc59a3e7] Failed to perform listing on remote host due to Connection refused: connect: java.net.ConnectException: Connection refused: connect
java.net.ConnectException: Connection refused: connect
at java.net.TwoStacksPlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at org.apache.commons.net.SocketClient._connect(SocketClient.java:243)
at org.apache.commons.net.SocketClient.connect(SocketClient.java:181)
at org.apache.nifi.processors.standard.util.FTPTransfer.getClient(FTPTransfer.java:592)
at org.apache.nifi.processors.standard.util.FTPTransfer.getListing(FTPTransfer.java:229)
at org.apache.nifi.processors.standard.util.FTPTransfer.getListing(FTPTransfer.java:192)
at org.apache.nifi.processors.standard.ListFileTransfer.performListing(ListFileTransfer.java:106)
at org.apache.nifi.processor.util.list.AbstractListProcessor.listByTrackingTimestamps(AbstractListProcessor.java:472)
at org.apache.nifi.processor.util.list.AbstractListProcessor.onTrigger(AbstractListProcessor.java:414)
at org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1176)
at org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:213)
at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:117)
at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

The solution to this problem was an inappropriate installation of the NiFi service which did not have user login information which had appropriate access to the server it was trying to access. It has been resolved now

Related

Can't connect DB with Teradata express studio

I have installed Teradata in my VM, and can connect the dbc database with the in-built Terraform studio express .
Now, I want to connect the dbc database with the Terraform studio express outside my VM i.e. in Windows. But when I try to test the connection using the same login details, it shows me "Ping Failed".
The detailed error message is as follows:
java.sql.SQLException: [Teradata JDBC Driver] [TeraJDBC 17.10.00.14] [Error 1277] [SQLState 08S01] Login timeout for Connection to 192.168.XXX.XX Mon Jan 10 19:39:51 IST 2022 socket orig=192.168.XXX.XX cid=50e21bd3 sess=0 java.net.SocketTimeoutException: connect timed out at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source) at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source) at java.net.AbstractPlainSocketImpl.connect(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF$ConnectThread.run(TDNetworkIOIF.java:1543)
at com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeDriverJDBCException(ErrorFactory.java:95)
at com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeDriverJDBCException(ErrorFactory.java:70)
at com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeIoJDBCException(ErrorFactory.java:208)
at com.teradata.jdbc.jdbc_4.util.ErrorAnalyzer.analyzeIoError(ErrorAnalyzer.java:59)
at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF.createSocketConnection(TDNetworkIOIF.java:188)
at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF.createIO(TDNetworkIOIF.java:174)
at com.teradata.jdbc.jdbc.GenericTeradataConnection.<init>(GenericTeradataConnection.java:290)
at com.teradata.jdbc.jdbc_4.TDSession.<init>(TDSession.java:186)
at com.teradata.jdbc.jdk6.JDK6_SQL_Connection.<init>(JDK6_SQL_Connection.java:36)
at com.teradata.jdbc.jdk6.JDK6ConnectionFactory.constructSQLConnection(JDK6ConnectionFactory.java:25)
at com.teradata.jdbc.jdbc.ConnectionFactory.createConnection(ConnectionFactory.java:181)
at com.teradata.jdbc.jdbc.ConnectionFactory.createConnection(ConnectionFactory.java:171)
at com.teradata.jdbc.TeraDriver.doConnect(TeraDriver.java:230)
at com.teradata.jdbc.TeraDriver.connect(TeraDriver.java:163)
at com.teradata.datatools.dtp.connectivity.db.teradata.TeradataJDBCConnection.makeConnection(TeradataJDBCConnection.java:286)
at com.teradata.datatools.dtp.connectivity.db.teradata.TeradataJDBCConnection.createConnection(TeradataJDBCConnection.java:124)
at org.eclipse.datatools.connectivity.DriverConnectionBase.internalCreateConnection(DriverConnectionBase.java:105)
at org.eclipse.datatools.connectivity.DriverConnectionBase.open(DriverConnectionBase.java:54)
at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.open(JDBCConnection.java:96)
at com.teradata.datatools.dtp.connectivity.db.teradata.TeradataPingFactory.createConnection(TeradataPingFactory.java:36)
at org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:83)
at org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:359)
at org.eclipse.datatools.connectivity.ui.PingJob.createTestConnection(PingJob.java:76)
at org.eclipse.datatools.connectivity.ui.PingJob.run(PingJob.java:59)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF$ConnectThread.run(TDNetworkIOIF.java:1543)
Please provide any solutions to fix this.
Note: I have also installed the Teradata tools and utilities suite (ODBC driver, BTEQ, etc)

JMeter distribution load testing Error: Connection refused to host

We are facing issues in JMeter remote testing. Master is stuck at:
Waiting for possible Shutdown/StopTestNow/Heapdump message on port 4445
While the client is throwing:
Connection refused to host exception
We are running master like below:
.\jmeter <b>-Djava.rmi.server.hostname=10.19.120.43 </b> -n -t .\Test.jmx -R 10.75.225.188
But in the slave side test completion status is sent to some other IP address:
2020-06-11 15:54:01,788 INFO o.a.j.e.RemoteJMeterEngineImpl: Creating JMeter engine on host 10.75.225.188 base '.'
<br>2020-06-11 15:54:01,788 INFO o.a.j.e.RemoteJMeterEngineImpl:<b> Remote client host: 10.19.120.43</b>
<br>2020-06-11 15:54:01,788 INFO o.a.j.s.FileServer: Set new base='.'
<br>2020-06-11 15:54:01,793 INFO o.a.j.e.RemoteJMeterEngineImpl: Cleaning previously set properties: {sample_variables=ulp_buffer_fill,ulp_lag_time,ulp_play_time,ulp_lag_ratio,ulp_dwn_time,ulp_hits,ulp_avg_chunk_time,ulp_avg_manifest_time}
2020-06-11 15:54:01,794 INFO o.a.j.e.StandardJMeterEngine: Applying properties {sample_variables=ulp_buffer_fill,ulp_lag_time,ulp_play_time,ulp_lag_ratio,ulp_dwn_time,ulp_hits,ulp_avg_chunk_time,ulp_avg_manifest_time}
<br>2020-06-11 15:54:01,795 INFO o.a.j.e.RemoteJMeterEngineImpl: Running test
<br>2020-06-11 15:54:01,797 INFO o.a.j.e.StandardJMeterEngine: Running the test!
<br>2020-06-11 15:54:01,797 INFO o.a.j.s.SampleEvent: List of sample_variables: [ulp_buffer_fill, ulp_lag_time, ulp_play_time, ulp_lag_ratio, ulp_dwn_time, ulp_hits, ulp_avg_chunk_time, ulp_avg_manifest_time]
<br>2020-06-11 15:54:22,801 ERROR o.a.j.s.RemoteListenerWrapper: testStarted(host) on 10.75.225.188
java.rmi.ConnectException: <b>Connection refused to host: 10.0.75.1; nested exception is:
java.net.ConnectException: Connection timed out: connect </b>
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source) ~[?:1.8.0_231]
at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source) ~[?:1.8.0_231]
at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source) ~[?:1.8.0_231]
at sun.rmi.server.UnicastRef.invoke(Unknown Source) ~[?:1.8.0_231]
at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(Unknown Source) ~[?:1.8.0_231]
at java.rmi.server.RemoteObjectInvocationHandler.invoke(Unknown Source) ~[?:1.8.0_231]
at com.sun.proxy.$Proxy20.testStarted(Unknown Source) ~[?:?]
at org.apache.jmeter.samplers.RemoteListenerWrapper.testStarted(RemoteListenerWrapper.java:79) [ApacheJMeter_core.jar:4.0 r1823414]
at org.apache.jmeter.engine.StandardJMeterEngine.notifyTestListenersOfStart(StandardJMeterEngine.java:217) [ApacheJMeter_core.jar:4.0 r1823414]
at org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJMeterEngine.java:384) [ApacheJMeter_core.jar:4.0 r1823414]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_231]
Caused by: java.net.ConnectException: Connection timed out: connect
at java.net.DualStackPlainSocketImpl.connect0(Native Method) ~[?:1.8.0_231]
at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source) ~[?:1.8.0_231]
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) ~[?:1.8.0_231]
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source) ~[?:1.8.0_231]
at java.net.AbstractPlainSocketImpl.connect(Unknown Source) ~[?:1.8.0_231]
at java.net.PlainSocketImpl.connect(Unknown Source) ~[?:1.8.0_231]
at java.net.SocksSocketImpl.connect(Unknown Source) ~[?:1.8.0_231]
at java.net.Socket.connect(Unknown Source) ~[?:1.8.0_231]
at java.net.Socket.connect(Unknown Source) ~[?:1.8.0_231]
at java.net.Socket.<init>(Unknown Source) ~[?:1.8.0_231]
at java.net.Socket.<init>(Unknown Source) ~[?:1.8.0_231]
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(Unknown Source) ~[?:1.8.0_231]
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(Unknown Source) ~[?:1.8.0_231]
... 11 more
FYI: this machine has docker running on it and 10.0.75.1 is associated with it
You need to EXPOSE port 1099 (or whatever port you're using as the server_port) in your Dockerfile (or use host network driver) and in the firewall of your 10.75.225.188 machine, this is the minimum requirement for JMeter master could establish the connectivity with the slave machine.
More information: Remote hosts and RMI configuration
You can also refer to JMeter Distributed Testing with Docker article, it has some sample networking configuration you might be willing to apply to your system

Master stuck on "Waiting for possible Shutdown/StopTestNow/HeapDump/ThreadDump message on port 4445"

I am performing a distributed testing and I have followed below steps.
Jmeter version on both Master and slave is same.
Java version is same on Master and slave.
Both the system are in same subnet, I can ping to slave from my master.
rmi key is created at master and copied to slave in bin folder.
slave IP address is added in remote_hosts
When I run simple test (using jmx) in non GUI mode from master to slave, I can see
Starting the test on host 10.1.11.85(fake ip here just for example)
Finished the test on host 10.1.11.85(fake ip here just for example)
On My master machine I can see
F:\Performance Testing\apache-jmeter-5.1.1\apache-jmeter-5.1.1\bin>jmeter.bat -n -R 10.1.56.65 -t
"F:\Performance Testing\Linkedin.jmx" -f -l "F:\Performance Testing\LoadTestData.csv" -e -o
"F:\Performance Testing\LoadTestData"
Picked up _JAVA_OPTIONS: -Xms512m -Xmx4096m
Creating summariser <summary>
Creating summariser <summary>
Created the tree successfully using F:\Performance Testing\Linkedin.jmx
Configuring remote engine: 10.1.56.65(Fake ip here for example)
Starting remote engines
Starting the test # Mon Sep 30 14:23:40 CEST 2019
Remote engines have been started
Waiting for possible Shutdown/StopTestNow/HeapDump/ThreadDump message on port 4445
And my script stop here even though I wait for 2hr its still same.
Script is not tiding up and not getting result.
When I did bit investigation and open jmeter-server.log file on slave machine I see:
java.rmi.ConnectException: Connection refused to host: 10.1.56.65;
nested exception is:
java.net.ConnectException: Connection timed out: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source) ~[?:1.8.0_211]
at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source) ~[?:1.8.0_211]
at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source) ~[?:1.8.0_211]
at sun.rmi.server.UnicastRef.invoke(Unknown Source) ~[?:1.8.0_211]
at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(Unknown
Source) ~[?:1.8.0_211]
at java.rmi.server.RemoteObjectInvocationHandler.invoke(Unknown Source) ~[?:1.8.0_211]
at com.sun.proxy.$Proxy21.testStarted(Unknown Source) ~[?:?]
at org.apache.jmeter.samplers.RemoteListenerWrapper.testStarted(RemoteListenerWrapper.java:79)
[ApacheJMeter_core.jar:5.1.1 r1855137]
at org.apache.jmeter.engine.StandardJMeterEngine.notifyTestListenersOfStart(StandardJMeterEngine.java:208)
[ApacheJMeter_core.jar:5.1.1 r1855137]
at org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJMeterEngine.java:381)
[ApacheJMeter_core.jar:5.1.1 r1855137]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_211] Caused by: java.net.ConnectException: Connection timed out: connect
at java.net.DualStackPlainSocketImpl.connect0(Native Method) ~[?:1.8.0_211]
at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source) ~[?:1.8.0_211]
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) ~[?:1.8.0_211]
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source) ~[?:1.8.0_211]
at java.net.AbstractPlainSocketImpl.connect(Unknown Source) ~[?:1.8.0_211]
at java.net.PlainSocketImpl.connect(Unknown Source) ~[?:1.8.0_211]
at java.net.SocksSocketImpl.connect(Unknown Source) ~[?:1.8.0_211]
at java.net.Socket.connect(Unknown Source) ~[?:1.8.0_211]
at sun.security.ssl.SSLSocketImpl.connect(Unknown Source) ~[?:1.8.0_211]
at sun.security.ssl.SSLSocketImpl.(Unknown Source) ~[?:1.8.0_211]
at sun.security.ssl.SSLSocketFactoryImpl.createSocket(Unknown Source) ~[?:1.8.0_211]
at org.apache.jmeter.rmi.SSLRMIClientSocketFactory.createSocket(SSLRMIClientSocketFactory.java:118)
~[ApacheJMeter_core.jar:5.1.1 r1855137]
... 11 more
I think so slave is not able to send result back to Master and getting connection refuse, how can I solve this?
Looking forward to hearing from you. (edited)
The fact you can ping the slave doesn't necessarily mean JMeter can communicate with it over RMI because your operating system firewall can allow ICMP traffic but block the ports JMeter is using.
By default JMeter uses port 1099 so double check that incoming connections are allowed. If not - either change the server.port property to use the port which is free and allowed or create a firewall rule unblocking the traffic.

H2 connecting to website via Shell "Connection is broken"

When running the command
C:\Program Files (x86)\H2\bin>java -cp h2.jar org.h2.tools.Shell -url "jdbc:h2:tcp://localhost/~/couponvalidationservice" -user "sa" -password "" -driver "org.h2.Driver"
I receive the following error. I'm not sure how to show the remaining 8 error messages. I am trying to connect to the website so that I can run some sql commands to configure it without opening the webportal.
Exception in thread "main" org.h2.jdbc.JdbcSQLException: Connection is broken: "java.net.ConnectException: Connection refused: connect: localhost" [90067-196] at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:168)
at org.h2.engine.SessionRemote.connectServer(SessionRemote.java:457)
at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:334)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:116)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:100)
at org.h2.Driver.connect(Driver.java:69)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at org.h2.tools.Shell.runTool(Shell.java:148)
at org.h2.tools.Shell.main(Shell.java:81)Caused by: java.net.ConnectException: Connection refused: connect
at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at org.h2.util.NetUtils.createSocket(NetUtils.java:103)
at org.h2.util.NetUtils.createSocket(NetUtils.java:83)
at org.h2.engine.SessionRemote.initTransfer(SessionRemote.java:115)
at org.h2.engine.SessionRemote.connectServer(SessionRemote.java:453)
... 8 more
I was able to resolve this connection issue by replacing the "tcp" section with "file:~/couponvalidationservice" this allowed me to connect and then run the SQL commands against the DB that I needed to.

JMeter - Getting Exception while running JMeter via GUI

I am trying to set up an aws server for performance testing of APIs where the logs will come. I installed Java and Jmeter on that server.
The application server is different i.e. test.server.com:8080
The aws server is different with different ip address.
The Jmeter GUI is installed on my laptop.
In my system in the apache Jmeter --> bin folder --> jmeter.properties, I have defined remote_hosts as ip address of the aws server where the logs should appear.
And server.rmi.localport=50000
I have not made any changes in the jmeter.properties file that is installed on aws server where the logs of performance testing should come.
When I run the Jmeter UI from my system and run --> remote start -> select the ip address of the aws server, it gives me connection time out exception.
In Logs am getting :
java.net.ConnectException: Connection timed out: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source)
at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
at sun.rmi.server.UnicastRef.newCall(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:54)
at org.apache.jmeter.engine.ClientJMeterEngine.<init>(ClientJMeterEngine.java:67)
at org.apache.jmeter.engine.DistributedRunner.createEngine(DistributedRunner.java:237)
at org.apache.jmeter.engine.DistributedRunner.getClientEngine(DistributedRunner.java:213)
at org.apache.jmeter.engine.DistributedRunner.init(DistributedRunner.java:93)
at org.apache.jmeter.gui.action.RemoteStart.doAction(RemoteStart.java:77)
at org.apache.jmeter.gui.action.ActionRouter.performAction(ActionRouter.java:80)
at org.apache.jmeter.gui.action.ActionRouter.access$000(ActionRouter.java:40)
at org.apache.jmeter.gui.action.ActionRouter$1.run(ActionRouter.java:62)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.awt.EventQueue.access$500(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(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)
Caused by: java.net.ConnectException: Connection timed out: connect
at java.net.DualStackPlainSocketImpl.connect0(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(Unknown Source)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(Unknown Source)
There is some configuration which has not been correctly done I believe. How can I check and what all changes should I make to run the test scripts.
Looks like network/firewall issue. Master & slaves should be in same subnet. If possible, you could create another instance in AWS and make it as a master. Ensure that jmeter master, slaves are able to talk to each other.
You might be behind the firewall. You can access AWS. But AWS can not access your machine/or the application behind the firewall.
Check if you are able to telnet through the specific port.
check AWS inbound/outbound rules.
If you use AWS, I would suggest you to use dokcer + rancherOS - It makes my life much easier in jmeter infrastructure setup.
http://www.testautomationguru.com/jmeter-distributed-load-testing-using-docker-rancheros-in-cloud/

Resources