...2.165.219.152
Error while downloading Custom Extraction
Connect to hosted.datascopeapi.reuters.com:443[hosted.datascopeapi.reuters.com/192.165.219.152] failed: Connection refused(Connection refused)
I forgot to give you this link: https://hosted.datascopeapi.reuters.com/RestApi.Help/Home/Diagnostics
Can you add unique Client Session Id's (GUIDs work great for this) to your requests, then start logging them BEFORE you start your request, and then tell us the ID of the failed calls?
Please open a Service Case so that our operations group can track if multiple clients are having any similar outcomes.
Do you use Client Session Id's on your calls ()? It is always helpful for you to have unique identifiers on each call in this case so that we can verify if the requests are even reaching our servers (which, I suspect not, this just allows me to confirm it).
Do you have any additional information to provide? Does this happen during high level of concurrency, or just single calls from your system? Does an immediate retry always work? Is it always to a specific endpoint or time of day? We are going to need more information to try and track this down.
We don't see this often to categorize it as yet. Below is the sample request to pull list of instruments which failed 3 times.
[2018-03-17 20:53:47,270] INFO [EXNG-REQ-PROC-T1] - RestJSONOverHTTP.restPost - Exception in restPost : /Search/HistoricalCriteriaSearch JsonObj: {"Request":{"Range":{"Start":"2018-03-17","End":"2018-03-17"},"ExchangeCodes":["1289"]}}com.mashape.unirest.http.exceptions.UnirestException: org.apache.http.conn.HttpHostConnectException: Connect to hosted.datascopeapi.reuters.com:443 [hosted.datascopeapi.reuters.com/192.165.219.152] failed: Connection refused (Connection refused)
We are not attaching any client session ID in the requests.
