Connection Reset Error in HTTPConnector Help!

Hi i have an HTTPConnector connected to an api call and since 10/11/2018 is not working properly, if i do the call with POSTMAN it works with no problem.

The error im recieveing is Connection Reset:

*************************** CloverETL Server Job: ****************************
CloverETL Server URL: http://ms001etl001:8080/clover
Sandbox code: rmartinez_dev
Job file: graph/RevelUPTest.grf
Run ID: 3248987
Refresh interval: 5 seconds
Connecting to CloverETL Server …
-------------------------------- Job log: ------------------------------------
2018-10-16 10:59:27,040 INFO 3248987 [http-apr-8080-exec-14] *** CloverETL, (c) 2002-2017 Javlin a.s. ***
2018-10-16 10:59:27,040 INFO 3248987 [http-apr-8080-exec-14] Running with CloverETL version 4.5.1 build#003 compiled 24/04/2017 21:44:51
2018-10-16 10:59:27,040 INFO 3248987 [http-apr-8080-exec-14] Running on 2 CPU(s), OS Windows Server 2012, architecture amd64, Java version 1.7.0_80, max available memory for JVM 8266752 KB
2018-10-16 10:59:27,040 INFO 3248987 [http-apr-8080-exec-14] License No. : CLSXXMESAL44797866BY
2018-10-16 10:59:27,040 INFO 3248987 [http-apr-8080-exec-14] License No. : CLSXXMESAL44797866BY
2018-10-16 10:59:27,052 INFO 3248987 [http-apr-8080-exec-14] Server 4.5.1. fingerprint: 3,528,778,058 jYtADOuQjM8llQ2YDO3kzN0QDTBNVRNhFWTx0QPzfxbFQN3QWMEx
2018-10-16 10:59:27,052 INFO 3248987 [http-apr-8080-exec-14] Executing job: rmartinez_dev/graph/RevelUPTest.grf with permissions of user “clover”
2018-10-16 10:59:27,052 INFO 3248987 [http-apr-8080-exec-14] Triggered via SOAP WS API
2018-10-16 10:59:27,065 INFO 3248987 [JobStarter_3248987] Initializing job id:1531244097499 hashCode:1991948944
2018-10-16 10:59:27,065 INFO 3248987 [JobStarter_3248987] Checking graph configuration…
2018-10-16 10:59:27,068 INFO 3248987 [JobStarter_3248987] Graph configuration is valid.
2018-10-16 10:59:27,068 INFO 3248987 [JobStarter_3248987] Graph initialization (Acquire_Employees)
2018-10-16 10:59:27,068 INFO 3248987 [JobStarter_3248987] Initializing phase 0
2018-10-16 10:59:27,068 INFO 3248987 [JobStarter_3248987] Phase 0 initialized successfully.
2018-10-16 10:59:27,068 INFO 3248987 [JobStarter_3248987] Initializing phase 1
2018-10-16 10:59:27,070 INFO 3248987 [JobStarter_3248987] Phase 1 initialized successfully.
2018-10-16 10:59:27,070 INFO 3248987 [JobStarter_3248987] Initializing watchdog
2018-10-16 10:59:27,071 INFO 3248987 [WatchDog_3248987] Job parameters:
CLOVER_USERNAME=clover
CONN_DIR=${PROJECT}/conn
DATAIN_DIR=${PROJECT}/data-in
DATAOUT_DIR=${PROJECT}/data-out
DATATMP_DIR=${PROJECT}/data-tmp
GRAPH_DIR=${PROJECT}/graph
GRAPH_FILE=graph/RevelUPTest.grf
JOBFLOW_DIR=${PROJECT}/jobflow
JOB_FILE=graph/RevelUPTest.grf
LIB_DIR=${PROJECT}/lib
LOOKUP_DIR=${PROJECT}/lookup
META_DIR=${PROJECT}/meta
NODE_ID=node01
PARENT_RUN_ID=3248987
PROFILE_DIR=${PROJECT}/profile
PROJECT=.
ROOT_RUN_ID=3248987
RUN_ID=3248987
SANDBOX_CODE=rmartinez_dev
SANDBOX_ROOT=E:\systemprofile/CloverETL/sandboxes/rmartinez_dev
SEQ_DIR=${PROJECT}/seq
SUBGRAPH_DIR=${GRAPH_DIR}/subgraph
TRANS_DIR=${PROJECT}/trans
inStore=
inURL=
2018-10-16 10:59:27,072 INFO 3248987 [WatchDog_3248987] Runtime classpath: [file:/E:/systemprofile/CloverETL/sandboxes/rmartinez_dev/trans/]
2018-10-16 10:59:27,072 INFO 3248987 [WatchDog_3248987] Disabled components:
2018-10-16 10:59:27,072 INFO 3248987 [WatchDog_3248987] [Trash:TRASH2] - Disabled: Always
2018-10-16 10:59:27,072 INFO 3248987 [WatchDog_3248987] [HTTPConnector:HTTPCONNECTOR2] - Disabled: Always
2018-10-16 10:59:27,074 INFO 3248987 [WatchDog_3248987] Starting up all nodes in phase [0]
2018-10-16 10:59:27,075 INFO 3248987 [WatchDog_3248987] Successfully started all nodes in phase!
2018-10-16 10:59:27,199 ERROR 3248987 [WatchDog_3248987] Component [HTTPConnector:HTTPCONNECTOR] finished with status ERROR. (Out0: 0 recs)
Connection reset
2018-10-16 10:59:27,200 ERROR 3248987 [WatchDog_3248987] Error details:
org.jetel.exception.JetelRuntimeException: Component [HTTPConnector:HTTPCONNECTOR] finished with status ERROR. (Out0: 0 recs)
at org.jetel.graph.Node.createNodeException(Node.java:636)
at org.jetel.graph.Node.run(Node.java:603)
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 sun.security.ssl.InputRecord.readFully(Unknown Source)
at sun.security.ssl.InputRecord.read(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:394)
at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:353)
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:141)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.jetel.component.HttpConnector.buildAndSendRequest(HttpConnector.java:2134)
at org.jetel.component.HttpConnector.process(HttpConnector.java:2092)
at org.jetel.component.HttpConnector.executeForRecord(HttpConnector.java:2247)
at org.jetel.component.HttpConnector.execute(HttpConnector.java:2211)
at org.jetel.graph.Node.run(Node.java:563)
… 3 more

2018-10-16 10:59:27,210 INFO 3248987 [WatchDog_3248987] Execution of phase [0] finished with error - elapsed time(sec): 0
2018-10-16 10:59:27,210 ERROR 3248987 [WatchDog_3248987] !!! Phase finished with error - stopping graph run !!!
2018-10-16 10:59:27,210 INFO 3248987 [WatchDog_3248987] -----------------------** Summary of Phases execution **---------------------
2018-10-16 10:59:27,210 INFO 3248987 [WatchDog_3248987] Phase# Finished Status RunTime(sec) MemoryAllocation(KB)
2018-10-16 10:59:27,210 INFO 3248987 [WatchDog_3248987] 0 ERROR 0 1758074
2018-10-16 10:59:27,210 INFO 3248987 [WatchDog_3248987] 1 N/A 0 0
2018-10-16 10:59:27,210 INFO 3248987 [WatchDog_3248987] ------------------------------** End of Summary **---------------------------
2018-10-16 10:59:27,210 INFO 3248987 [JobFinalizer_3248987] Finalization
2018-10-16 10:59:27,210 INFO 3248987 [WatchDog_3248987] WatchDog thread finished - total execution time: 0 (sec)
2018-10-16 10:59:27,211 INFO 3248987 [JobFinalizer_3248987] RunTime: 175 ms
2018-10-16 10:59:27,211 ERROR 3248987 [JobFinalizer_3248987]
---------------------------------- Error details -----------------------------------
Component [HTTPConnector:HTTPCONNECTOR] finished with status ERROR. (Out0: 0 recs)
Connection reset
------------------------------------------------------------------------------------
2018-10-16 10:59:27,211 INFO 3248987 [JobFinalizer_3248987] Finished Status: ERROR

See details of execution #3248987

The api call is the following:

https://phenomenom.revelup.com/resource … ormat=json

Server has no proxy.

The api authentication is via HTTP Header.

Hello Ricardo,

it seems that the API site you intend to connect to has stopped supporting TLS protocols older than version 1.2. Unfortunately, due to the obsolescence of Java which you are using on your server (1.7.0_80) which does not support TLS 1.2 by default, the SSL handshake could not be established between the API site and CloverETL Server. The most straight-forward solution to this situation would be to upgrade to Java 8.

Best regards,

Updated Clover Java to Java 8 and sucessfully fixed the issue, Thanks!