Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
please help, this error show in job server console. job run as well but why this message shown. see full log in this attachment.
ERROR MultiSocketServer - java.net.SocketException: Connection reset
org.talend.remote.commons.exception.ClientServerException: java.net.SocketException: Connection reset
at org.talend.remote.server.AbstractObjectServerSocket.initInputStream(AbstractObjectServerSocket.java:65)
at org.talend.remote.server.AbstractObjectServerSocket.initAfterSocketInitialized(AbstractObjectServerSocket.java:46)
at org.talend.remote.server.AbstractServerSocket.start(AbstractServerSocket.java:39)
at org.talend.remote.server.MultiSocketServer$3.run(MultiSocketServer.java:321)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(Unknown Source)
at java.net.SocketInputStream.read(Unknown Source)
at java.io.ObjectInputStream$PeekInputStream.read(Unknown Source)
at java.io.ObjectInputStream$PeekInputStream.readFully(Unknown Source)
at java.io.ObjectInputStream$BlockDataInputStream.readShort(Unknown Source)
at java.io.ObjectInputStream.readStreamHeader(Unknown Source)
at java.io.ObjectInputStream.<init>(Unknown Source)
at org.talend.remote.server.AbstractObjectServerSocket.initInputStream(AbstractObjectServerSocket.java:59)
... 6 more
Hello,
In order to address the issue I would require additional details and you can also try the below steps if helps to fix the issue.
Thanks
Kavya S
Also a windump or tcpdump would be highely appreciated to troubleshoot this network error
1. What is the Talend version used?
>> 7.2
2. Please make sure jobserver is up and running and able to connect from TAC, execute command netstat or ping
>> jobserver is up, no problem with execution. ping is successfully
3. Clean the TAC cache temp and work folder
>> done. but still shown error
4. Please make sure the jobserver is started with the correct user and check the permission of the jobserver folders.
>> already started. job running well