[resolved] Talend Studio Remote Server Connecting to Socket Refused

One Star

[resolved] Talend Studio Remote Server Connecting to Socket Refused

I have a Talend Administrator Center and Job server running in AWS (same instance)
When i run the job using Talend Platform for Data Management 5.5.1 on remote server (AWS Job server).
It returns " connection refused" but the job runs successfully on Job server. The problem is I can not see the messages which should return from server.
But when I forward the ports (3334 to 4445) to my computer's private ip on my router, it works 100% fine.
Any suggestions would be greatly appreciated.
Error Message:
Checking ports...
Sending job 'testjob' to server (JobServer IP:8001)...
File transfer completed.
Deploying job 'testjob' on server (JobServer IP:8000)...
Running job 'testjob'...
Starting job testjob at 20:52 09/10/2014.

connecting to socket on port 3631
connection refused
0|20141010005314_RTval|20141010005314_RTval|20141010005314_RTval|testjob|start job||20141009205316.096-0400
Unable to connect to "My Public IP" on the port 3631
1|20141010005314_RTval|20141010005314_RTval|20141010005314_RTval|OnComponentOk1|ok|start
1|20141010005314_RTval|20141010005314_RTval|20141010005314_RTval|If1|clear
.....
.....

Accepted Solutions
Seventeen Stars

Re: [resolved] Talend Studio Remote Server Connecting to Socket Refused

The problem with the statistics is it always use different IP ports. You can configure the IP port range in the studio but it remains a range. I suggest you take care for a transparent network between TAC and job server.
To be honest the decision for a none stable IP port for the statistics is not easy to understand for me. 
In the TAC you can - and should - switch off the statistics for the task in the task settings. In the studio you can switch off the statistics in the Run view under advanced settings.

All Replies
Seventeen Stars

Re: [resolved] Talend Studio Remote Server Connecting to Socket Refused

The problem with the statistics is it always use different IP ports. You can configure the IP port range in the studio but it remains a range. I suggest you take care for a transparent network between TAC and job server.
To be honest the decision for a none stable IP port for the statistics is not easy to understand for me. 
In the TAC you can - and should - switch off the statistics for the task in the task settings. In the studio you can switch off the statistics in the Run view under advanced settings.
One Star

Re: [resolved] Talend Studio Remote Server Connecting to Socket Refused

thanks jlolling
I disable the statistics setting in Talend studio and now it works fine.
One Star

Re: [resolved] Talend Studio Remote Server Connecting to Socket Refused

Hello,
We have a similar problem with the production talent jobs which try to run the statistics but fail to connect to the random port.
In the Talend Open Studio for Data Integration, when I uncheck the 'Statistics' box, the do not run.
How can I disable this feature in the production (built jobs) as well ?
Thank you.
One Star

Re: [resolved] Talend Studio Remote Server Connecting to Socket Refused

Hello, 
I am having a similar issue with Talend 6 Big Data Platform, if I run the job from the studio in a remote job server it works fine but not showing statistics,  if I do debug run it fails with the error below. 
the problem is that if I run the job from the TAC it keeps waiting for the execution and never executes. 
The ports are open in the IPTABLES (Ubuntu server), but the job server doesn't seem to be using them. 
Any recomendations?

Starting job ConfigTest at 16:11 05/11/2015.

connect to commandline server:  Commandline server 1 (10.0.50.172:8002)
send command to commandline server...
InitRemoteCommand initRemote
COMPLETED at Thu Nov 05 16:11:48 EST 2015
LogonProjectCommand log on CONFIGTESTPROJECT(trunk)
COMPLETED at Thu Nov 05 16:11:49 EST 2015
ExecuteJobOnServerCommand ConfigTest on server JobServer2 context Default version 0.1
COMPLETED at Thu Nov 05 16:12:04 EST 2015
  execution result for ConfigTest
    Exit Value : 1
    StdOut : Execution on server JobServer2 (Local Job Server)
### Job STARTED  at 2015/11/05 16:12:04 (jobId=o6rUDrf7, jobExecutionId=20151105161204_SlMfV) ###
connecting to socket on port 4334
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at java.net.Socket.connect(Socket.java:538)
at java.net.Socket.<init>(Socket.java:434)
at java.net.Socket.<init>(Socket.java:211)
at routines.system.RunTrace.startThreadTrace(RunTrace.java:51)
at configtestproject.configtest_0_1.ConfigTest.runJobInTOS(ConfigTest.java:1095)
at configtestproject.configtest_0_1.ConfigTest.main(ConfigTest.java:975)
Exception in thread "main" java.lang.NullPointerException
at routines.system.RunTrace.stopThreadTrace(RunTrace.java:77)
at configtestproject.configtest_0_1.ConfigTest.runJobInTOS(ConfigTest.java:1150)
at configtestproject.configtest_0_1.ConfigTest.main(ConfigTest.java:975)
### Job ENDED WITH ERROR  at 2015/11/05 16:12:04 (jobId=o6rUDrf7, jobExecutionId=20151105161204_SlMfV) ###

LogoffProjectCommand log off
COMPLETED at Thu Nov 05 16:12:04 EST 2015
Job ConfigTest ended at 16:12 05/11/2015.