On VB.NET application ethernet connection timing out after few hours

Question

0.00/5 (No votes)

See more:

Hi guys, I wrote Vb.net code for controlling a robot which communicated using ethernet. everything is working fine but after a while (about 6-7hours) it looses communication probably due to buffer memory or something getting full and it throws following error-Unable to read data from the transport connection: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.

So how do I increase buffer memory or how do I get it empty regularly so connection always stays active. I'm using below code for streaming data-

_tcpClient = New System.Net.Sockets.TcpClient()
_tcpClient.Connect("193.240.200.203", 10001)
_tcpStream = _tcpClient.GetStream()
_tcpStream.BeginRead(_readBuffer, 0, 256, New AsyncCallback(AddressOf OnDataAvailable), Nothing)

Thanks in advance, any help much appreciated.

What I have tried:

I was thinking to increase read buffer size from 256 to 1024 and see if it works but haven't got it done yet.

_tcpStream.BeginRead(_readBuffer, 0, 1024, New AsyncCallback(AddressOf OnDataAvailable), Nothing)

Posted 18-Nov-20 5:40am

Member 13936585

Updated 18-Nov-20 6:46am

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)

Gerry Schmitz · Answer 1 · 2020-11-18T06:46:00

You add error handling / reporting before "fixing" it.

You need to know more about the situation that causes a problem. Then when the problem occurs, dump stats like "byte counts", etc.

In a "mission critical" situation you write monitors for recording reads, writes, timeouts.

You're asking if you should just throw code at it. No.