full holdings for a fund and ETF DSS Rest API request generates Http error code : 408

Since 01.02.2021 i am getting below error:

java.io.IOException: Server returned HTTP response code: 408 for URL: https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractWithNotes

I am using below DSS Rest API refinitiv request for full holdings for a fund and ETF in my java code:

"ExtractionRequest": {
            "@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.FundAllocationExtractionRequest",
            "ContentFieldNames": [
              "Security Description",
              "Allocation Asset Type",
              "Allocation Date",
              "Allocation Item",     
              "Allocation Percentage",      
              "Allocation ISIN",      
              "Market Value Currency",
              "Market Value Held"     
            ],
            "IdentifierList": {
              "@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
              "InstrumentIdentifiers": [%s],
              "ValidationOptions": null,
              "UseUserPreferencesForValidationOptions": false
            },
            "Condition": {
              "FundAllocationTypes": [
                "Asset",
                "Currency",
                "FullHoldings",
                "IndustrySector",
                "InvestmentCountry",
                "TopTenHoldings"
              ]
            }
          }
        }

Below is connection request to url:

//Connection to the URL string https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/ExtractWithNotes
    private static HttpURLConnection connection(String urlSpec) {
        HttpURLConnection connection = new URL(urlSpec).openConnection() as HttpURLConnection

        connection.setRequestProperty('Accept', 'application/json')

        connection.setRequestMethod("POST")
        connection.setRequestProperty("Content-Type", "application/json; utf-8")
        connection.setDoOutput(true)
        connection
    }

We are using the same API request since December 2020 but did not face any issue. We are running this process request everyday at 5am CET in the morning. Now if we try to run the process again at 1pm CET then it runs without any issue.

This is very critical issue for us.

Find more posts tagged with

dss

funds

etf

dss-rest-api

datascope-select

error-408

Accepted answers

zoya faberov

Hello @rahul.deshmukh,

My understanding from reading the question is that the code is running successfully at some times, but not at other. And this is a repeatable behavior, has happened more then once.

Therefore, we have to assume there is no issue with code.

A much likelier cause is connectivity or service availability issue. Especially, as 408 error is from timeout family of errors.

This forum is targeted at general questions and discussions targeted at Refintiiv API usage, the majority of the forum members are Refinitiv API developers, the moderators of the forums are Refinitiv API experts.

Datascope product support can help you, as a customer, to investigate this type of issue, and especially for a critical issue, in the future, would suggest raising this type of issue directly with Refinitiv Helpdesk Online -> Datascope.

At this time, have raised on your behalf, case # is 09586128 , please expect direct communication by email from DSS support team.

I would suggest investigating in parallel, with your local network admin/group, if any maintenance or network connectivity outages have coincided with your failed submission times- if you find out this is the case - please let us know.

All comments

Gurpreet

Hi @rahul.deshmukh

HTTP 408 means request timeout - and that is what you are experiencing when your request works some times and not other. This could be happening due to the additional load on the DSS server during that time, or due to network contention on your side. Either way, with a long running extraction like yours, it is never a good idea to use synchronous request.

I would recommend that you try asynchronous request and make your application more robust to handle the error conditions. You can see the example of async in the Java and C# examples here. Add a HTTP header:

"Prefer", "respond-async, wait=60"

and keep checking your response for HTTP 202, until you get a HTTP 200.

zoya faberov

Hello @rahul.deshmukh,

My understanding from reading the question is that the code is running successfully at some times, but not at other. And this is a repeatable behavior, has happened more then once.

Therefore, we have to assume there is no issue with code.

A much likelier cause is connectivity or service availability issue. Especially, as 408 error is from timeout family of errors.

At this time, have raised on your behalf, case # is 09586128 , please expect direct communication by email from DSS support team.

rahul.deshmukh

please check my previous question in forum https://community.developers.refinitiv.com/questions/67550/full-holdings-for-a-fund-and-etf-dss-rest-api-requ.html?childToView=68146#comment-68146 where it has been mentioned that i should remove this line from http request:

connection.setRequestProperty('Prefer', 'respond-async')

rahul.deshmukh

Will be really helpful here if you can help here to resolve this issue. What changes i have to do in http request ? I confirmed from our side and there is no proxy or network connection issues.

rahul.deshmukh

I already confirmed from our side and we dont have any proxy or network connection issues. If you run the same request again different time it works then why it failed during sometimes ?

zoya faberov

Hello @rahul.deshmukh,

We can try and suggest, helping is our goal. However, many environment-specific issues do not yield themselves to resolution within the framework of the discussion forums.

I second @Gurpreet on the approach. I would try, in addition:

1. Include additional code, to resubmit the request on status 408 and document the resubmit, and consequently, review "the pattern". Once the status becomes 202 or 200, if it is 202, would keep checking status periodically (as shown in our examples), till it becomes 200, once the status is 200 would retrieve the result.

2. Consider, how large is your instrument list? How long does your request take, on average, at the time when it completes? Fund allocation request limit is 600 at this time, according to DSS Extraction Limits, if you are coming close to the limit, I would, as well as verifying to request async, as suggested by @Gurpreet, test dividing the request into several sub-lists, to see if this allows your request not to timeout at the times of high service load. Just a guess here, are any of the identifiers Chain RICs, and being expanded into many RICs as part of the request - then would count how many RICs in total, when expanded, and approach accordingly.

EXPLORE OUR SITES