Problem with NetworkStream.ReadTimeout property

Question

4.00/5 (2 votes)

See more:

.NET2.0

The ReadTimeout property of that class seems to work only once. I create the objects as follows:

this.mySocket = new TcpClient();
this.mySocket.Connect(this.ipAddress,this.tcpPort);
this.stream = this.mySocket.GetStream();
this.stream.ReadTimeout = this.Timeout;

I have a ReceiveFrame function similar to this:

C#

public override void ReceiveFrame(byte[] buf,out int longitud)
{
    longitud = 0;
    try
    {
        longitud = this.stream.Read(buf, longitud, buf.Length);
    }    
    catch (SocketException)
    {
    }
    catch (IOException)
    {
        //Debug.Assert(this.mySocket.Connected);
    }
}

It receives fine. When a frame doesn't arrive on time the timeout occurs as expected. After that situation making another attempt to transmit and receive may work if new data arrive, but the expected timeout never occurs again in case they don't.

It's curious that when the first timeout occurs it says that socket.Connected is false (although still connected, giving an error if you try to connect again).

Does anybody know how to make ReadTimeout keep on working? Thanks,

Ruben.

Posted 5-Oct-10 22:34pm

rcastilloprado

Updated 12-Dec-10 2:45am

Abdul Quader Mamun

v2

Add a Solution

Comments

Abdul Quader Mamun 12-Dec-10 8:46am

Spelling check.

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)

Sergey Alexandrovich Kryukov · Answer 1 · 2010-12-10T04:58:00

Do not shut up exception propagation by providing empty exception handler (in practice, do it less often then never:); I hope this is what you really do in real life).

I think once you specify ReadTimeout, it always work. But! chances are you have overlooked the situation when either SocketException or IOException was thrown even before entering your thread's wait state. This is by far the most typical reason for the problems of a kind you observe.
Provide a full dump of those two exceptions (do not do this assertion you commented out) and you will see the result, analyze it.

If you have caught one of the exception but fail to figure out the problem, please submit the text of your dump here so I could see it.

To provide good exception dump, you could use, for example, my code I advice in different answer, here.

Thank you.