Socketexception ONLY during low network bandwidth

Question

0.00/5 (No votes)

See more:

Friends, We had a client / server system. Around 1 GB of data flows in a specific use case from Client to Server. This is pushed via socket. While we have > 10 Mbps network speed looks like all goes well.

But ONLY during low network bandwidth we see Socket exception

Failed in remoting call to server ---> System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

What I have tried:

This seems to be random earlier. But identified this is only due to network speed.

Posted 1-Nov-21 0:17am

ptr_Electron

Updated 1-Nov-21 0:53am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2021-11-01T00:53:00

It's probably a timeout problem: start by looking at your code - we can't do that for you, we don't have it - and look for timeouts you can extend.
Socket Class (System.Net.Sockets) | Microsoft Docs[^]
It's probably either the ReceiveTimeout or the SendTimeout, but you'll probably need to measure the time it's taking and establish a worse case before you start playing or ot'll come back later at an importune moment.