DSS REST API: error on receiving an extraction result that looks like some timeout problem

I am currently testing again my .Net app that uses the DSS REST API, and, not for the first time, after having extracted successfully a number of times, when I restart my app after a change, I get an error on getting the extractionResult, the error messge is:

"Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host."

My app logs in using the ExtractionsContext with user and pw, so it can be that it logged in say 5 or 6 times, and then I hit a bug in my code, so I just stop the app. And after a number of stops, I get this weird error.

And then I keep getting that error for a while if I start m app again.

Is there a proper way to log out of DSS, which would maybe cure that problem ?

Or is there a timeout, and after some hours, the DSS systems just sever the connection ?

So, what can I do about that, what the right way to handle this situation. When everything works well, my whole app runs in 1,5 minutes, so it's a lightweight thing

Thanks for help

Bernard

Find more posts tagged with

connection

dss

dss-rest-api

datascope-select

Accepted answers

BTh

Hi Christiaan

I think I cried wolf. I had a mix up in my app config file, so that I was trying to update old tables with a slightly different structure. Fixing that allowed me to run the app successfully twice today, and the scheduled just ran successfully, so let's see if it continues to be OK

However, last week I did have one occurrence of the connection closed, so I will continue to watch out for that.

And yes, my app traffic certainly does go through firewalls and proxies. Timeout can hardly the problem, as wait times are low (10-20 seconds) due to low volumes.

Thanks

Bernard

All comments

Ramprasad.Kumaralu.J

Hi @BTh: this seems to be a user-specific issue. Would please raise a CASE with Refinitiv support along with your user details to address this issue. Thank you

Christiaan Meihsl

@BTh, just to answer this specific query: "Is there a proper way to log out of DSS ?": no, there is none.

BTh

OK, then this closed connection is something unexpected, which I will have to deal with. When it happens, it usually last for quite a while until suddenly the request/response works again. As my app is going to be scheduled to run every day at a given time, I will have to find a way to rerun it automatically after a while if this error happens...

Christiaan Meihsl

@BTh, I confirm it is something unexpected, this should not occur.

Raising a case would allow the product team to trace your connection and investigate why the connection was closed.

That said, I suspect that when you have finished debugging your app this issue will no longer occur, because your app will only run once a day.

BTh

Hi Christiaan

However, last week I did have one occurrence of the connection closed, so I will continue to watch out for that.

And yes, my app traffic certainly does go through firewalls and proxies. Timeout can hardly the problem, as wait times are low (10-20 seconds) due to low volumes.

Thanks

Bernard

Christiaan Meihsl

@BTh, glad to read it seems solved. Keep us posted if the issue ressurfaces.

EXPLORE OUR SITES