logo
down
shadow

Explanation: The underlying connection was closed: The connection was closed unexpectedly


Explanation: The underlying connection was closed: The connection was closed unexpectedly

By : user2953739
Date : November 21 2020, 01:01 AM
should help you out
The underlying connection was closed: The connection was closed unexpectedly
code :


Share : facebook icon twitter icon
System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly

System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly


By : Property Leo
Date : March 29 2020, 07:55 AM
wish of those help I encountered the same exception a while ago and I remember that this happens in some cases due to a bug in .NET. You can work around this by setting the Timeout and ReadWriteTimeout of the request to higher values, or set KeepAlive to false.
This would only be a workaround, though, so I suggest you try to find the actual root cause before assuming anything.
WCF with Entity Framework 6.0 error "The underlying connection was closed: The connection was closed unexpectedly&q

WCF with Entity Framework 6.0 error "The underlying connection was closed: The connection was closed unexpectedly&q


By : Charles Stephane
Date : March 29 2020, 07:55 AM
this one helps. It looks like OData related components needed to be upgraded also (See this link).
The underlying connection was closed: The connection was closed unexpectedly. Data is too big?

The underlying connection was closed: The connection was closed unexpectedly. Data is too big?


By : afterlife24
Date : March 29 2020, 07:55 AM
I hope this helps . What is your client-side configured as? You've displayed your server-side configuration, but don't forget that the client-side has it's own configuration settings.
Looking at your server-side configuration, it appears that the violation is occurring on the reception of the data on the client.
code :
// Apply the DataContract to the type
[DataContract]
public class RFData
{
    // Apply the DataMemberAttribute to the various properties
    [DataMember]
    public double RFDouble { get; set; }
    [DataMember]
    public int RFInt { get; set; }
    [DataMember]
    public string RFString { get; set; }
}
nuget.exe push throws error. The underlying connection was closed: The connection was closed unexpectedly

nuget.exe push throws error. The underlying connection was closed: The connection was closed unexpectedly


By : user2970592
Date : March 29 2020, 07:55 AM
around this issue I solved this by putting retry and timeout.
code :
steps {
    script {
        echo "Publishing packages"
        retry(3) {
            timeout(time: 30, unit: 'MINUTES') {
                echo "Publish large file."
                bat "_________"
            }
        }
    }
}
httpWebRequest (The underlying connection was closed: The connection was closed unexpectedly.)

httpWebRequest (The underlying connection was closed: The connection was closed unexpectedly.)


By : Parikshit Sharma
Date : March 29 2020, 07:55 AM
I wish did fix the issue. I write a bit about how Fiddler can "magically" fix things here: http://blogs.telerik.com/fiddler/posts/13-02-28/help!-running-fiddler-fixes-my-app-
The issue you're encountering is actually a bug in the .NET Framework itself. The rules of HTTP are such that the server may close a KeepAlive connection at any time after sending the first response (e.g. it doesn't need to accept another request on the connection, even if the client requested KeepAlive behavior).
shadow
Privacy Policy - Terms - Contact Us © ourworld-yourmove.org