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

BTh
BTh Contributor
in DSS

Hi

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

Tagged:

Best Answer

  • BTh
    BTh Contributor
    Answer ✓

    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

Answers

Categories