RemoteDisconnected: Remote end closed connection without response

khaoula.riad-ext
khaoula.riad-ext
in Refinitiv Data Platform

Hello,

While trying to download tick history data, we get at first a response with status code 202 , then it keeps pooling for many minutes ( sometimes hours) without response until we get the following exception :

- HTTPSConnectionPool(host='selectapi.datascope.refinitiv.com', port=443): Max retries exceeded with url: /RestApi/v1/Extractions/ExtractRawResult(ExtractionId='0x08bad7f94939549f') (Caused by ProxyError('Cannot connect to proxy.', RemoteDisconnected('Remote end closed connection without response')))

Can you please advise on this issue ?

Tagged:

Best Answer

  • Jirapongse
    Jirapongse
    Answer ✓

    @khaoula.riad-ext

    Thank you for reaching out to us.

    How often did the application poll for the data?

    Typically, the application needs to wait for several minutes (3-5 minutes) before each polling.

    According to the error, it may relate to the proxy.

    - HTTPSConnectionPool(host='selectapi.datascope.refinitiv.com', port=443): Max retries exceeded with url: /RestApi/v1/Extractions/ExtractRawResult(ExtractionId='0x08bad7f94939549f') (Caused by ProxyError('Cannot connect to proxy.', RemoteDisconnected('Remote end closed connection without response')))

    Does the application use a proxy server to connect to the DataScope Select server? You may contact your IT support team to verify if there is a proxy server installed on your machine or system.



Answers

  • una.keller
    una.keller

    Hi @Jirapongse

    I am facing a similar issue

    HTTPSConnectionPool(host='selectapi.datascope.refinitiv.com', port=443): Max retries exceeded with url: /RestApi/v1/Extractions/ExtractWithNotes (Caused by ProxyError('Cannot connect to proxy.', RemoteDisconnected('Remote end closed connection without response')

    With this payload

    payload = '{"ExtractionRequest": {"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.HistoricalReferenceExtractionRequest", "ContentFieldNames": ["RIC", "Security Description", "Put Call Flag", "Expiration Date", "Strike Price"], "IdentifierList": {"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList", "InstrumentIdentifiers": [{"Identifier": "0#TY+", "IdentifierType": "ChainRIC"}], "ValidationOptions": {"AllowHistoricalInstruments": true}, "UseUserPreferencesForValidationOptions": false}, "Condition": {"ReportDateRangeType": "Range", "QueryStartDate": "2024-01-22", "QueryEndDate": "2024-01-23"}}}'

    It works with a different chain RIC however

    '{"ExtractionRequest": {"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.HistoricalReferenceExtractionRequest", "ContentFieldNames": ["RIC", "Security Description", "Put Call Flag", "Expiration Date", "Strike Price"], "IdentifierList": {"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList", "InstrumentIdentifiers": [{"Identifier": "0#G1TW+", "IdentifierType": "ChainRIC"}], "ValidationOptions": {"AllowHistoricalInstruments": true}, "UseUserPreferencesForValidationOptions": false}, "Condition": {"ReportDateRangeType": "Range", "QueryStartDate": "2024-01-22", "QueryEndDate": "2024-01-23"}}

    I thought it might be volume related but issue persists when only querying 2 dates at a time. The same chain "0#TY+" works fine in postman directly.

    Any idea why it errors with one chainRIC and not another?

  • Jirapongse
    Jirapongse

    @una.keller

    Acorrding to the error (Caused by ProxyError), it relates to the proxy server used in the environment. You can contact your IT support team to verify what the problem is. It may relate to the HTTP timeout.

Categories