we are having the following issue randomly in different web service calls:
"The underlying connection was closed: A connection that was expected to be kept alive"
I have a support case open with OutSystems, but I remembered maybe one of you guys already had this issue before and might have a solution for this.
So far, what I've found was setting a 'KeepConnectionAlive' property to FALSE, which concerns us. Because it could impact performance since it goes against the default behavior of the HttpWebRequest class in keeping connections alive to re-use them.
Do you guys have any other idea where could we mess around to fix this?
Just an update. No one had this issue before?
Possible networking issues.
I have this same issue!
My case is deterministic (an input always fails and another always returns OK).
My first guess is to blame the Webservice Server but SOAP UI returns Ok in both cases!
I don't know if its related but the input that returned error is bigger (> 1MB)