This is true for different kinds of requests we're using. Last failor was yesterday, but after some manual re-starts Composite, Corporate Actions, Premium End of Day requests finished ok, but not Timeseries request. It was fixed within next few hours. What's a cause of this? Is it possible to get any related info about the error in order to make sure the request will be successful after re-start?
For a deeper look into our DataScope Select REST API, look into:
Overview | Quickstart | Documentation | Downloads | Tutorials
41
●1 ●3 ●7
Some times (once per 2-3 weeks) dss api requests are failing with "Stream was not readable" exception
Hello @nazar.viliura,
We would like to help and would like to collect more information.
Have you seen it happen since then? Is this something that happened once, or have you seen it more then once? Have only one request been impacted, or for duration of time, or till restart?
Thanks,
-AHS
Hello Zoya,
yes, recently it appears quite often. Same exception I saw today and yesterday. Current error behavior is very different from time to time: it could be eliminated during next restart (most often option) or still be failing during 5 or even more restarts. The most often the error occur during TimeSeries, next are Composite and PremiumEndOfDay requests. The most rare case is CorporateActionsStandard one.
Also, very rarely there could be another message in combination with this one saying smth like 'cannot write data to a stream'. Please, tell me if you need more info.
Thanks
Hello @nazar.viliura ,
Could you please add the specific TimeSeries request that you are issuing,
and also how, via .Net SDK, python, Java?
Does the issue manifest at the same time via naked request, for example, Postman, or not?
It would be very helpful if you could open a service request exactly when it is happening, so that we, on our side, can try to catch it while it's still happening and reproduce it?
Thanks in advance,
-Zoya
hi @zoya.farberov,
requests are send via .net sdk and based on ThomsonReuters DSS api examples.
This is how the request looks like:
new TimeSeriesExtractionRequest
{
IdentifierList = InstrumentIdentifierList.Create(identities, null, false),
ContentFieldNames = "Instrument ID", "Instrument ID Type", "Trade Date","Close Price","Universal Close Price","Open Price","High Price", "Low Price","Volume","Currency Code"
Condition = new TimeSeriesCondition { StartDate = startDate, EndDate = endDate, }
};
where identities - list of instruments basically of RIC type.
One more could be helpful: today, on 08/11/2017, in time period of 7.25am - 8.10am there were made composite, timeseries, corp actions, premium end of day pricing requests, which all failed. UserId: 9010761.
Hope this helps in your investigations.
Thanks
Hello @nazar.viliura,
A support case was opened to investigate the issue.
Case # is 05830559.
We will contact you via email for further details.
-AHS
Checked the associated case 05830559 status, it is still in progress. So, I just extended its triage then.
41
●1 ●3 ●7
Cannot reproduce the issue any more. Possible reason is in our local network configuration.
