Forum Discussion
All API calls failing after the 3rd consecutive call...
- Anonymous9 years ago
For the record, I found a temporary solution for this until they fix this bug: Closing the ConnectionGroup after each WebRequest is completed.
Assuming "wr" is your HttpWebRequest var, just use this line after you call wr.GetResponse.
wr.ServicePoint.CloseConnectionGroup(wr.ConnectionGroupName)
No more timeouts after the 2nd API POST call.
OK, this appears to only be affecting POST calls. I can run GET calls as many times as I want, but on the third POST call, it always times out. I shouldn't have been including the call to get the list of Datasets in my count, since that's a GET call, so it isn't after the 3rd API call (in general) that I get timeouts, but on the 3rd POST call.
Anonymous wrote:
OK, this appears to only be affecting POST calls. I can run GET calls as many times as I want, but on the third POST call, it always times out. I shouldn't have been including the call to get the list of Datasets in my count, since that's a GET call, so it isn't after the 3rd API call (in general) that I get timeouts, but on the 3rd POST call.
Anonymous
Thanks for reporting this issue, I could reproduce the similar timeout on the 3rd POST call. I'm going to escalate this internally and would post back if I get any update.