Re: Socket.ReceiveTimeOut Problem - C# Discussion Boards

8-Dec-09 23:35

Hi All,

When I set the ReceiveTimeOut of Socket to some milliseconds then Socket throws the timeout Exception while the period expires and the problem is that then Socket is disconnected therefore i am unable to send and receive again with this socket.
I want that it waites for sometime for receiving but after elapsing the time,it should not be disconnected so that i can use it again n again..

Plz help...Its urgent.

Best Regards,
Lalit Narayan

Programm3r9-Dec-09 0:22

9-Dec-09 0:22

From MSDN:

The ReceiveTimeout property determines the amount of time that the Read method will block until it is able to receive data. This time is measured in milliseconds. If the time-out expires before Read successfully completes, TcpClient throws a IOException. There is no time-out by default.

Read more here[^].

Kind regards,

The only programmers that are better C# programmers, are those who look like this -> Green Alien | [Alien]

Programm3r
My Blog: ^_^

lnmca9-Dec-09 0:27

9-Dec-09 0:27

But when the socket throws exception ,socket is disconnected...this creates the problem 4 me,plz give the solution so that the socket should not be disconnected.

Best Regards,
Lalit Narayan

Programm3r9-Dec-09 0:44

9-Dec-09 0:44

I think that is what happens when the time-out period is exceeded, the Receive method will throw a SocketException. Have you tried catching the exception, checking whether the socket is still connected (see here[^]), if not try to reconnect...

The only programmers that are better C# programmers, are those who look like this -> Green Alien | [Alien]

Programm3r
My Blog: ^_^

lnmca9-Dec-09 0:57

9-Dec-09 0:57

Hi,

Actually i am working on Server Side,the connection requests comes from the Client Side,i can not reconnect to the Client through Socket....
The Server has TCP Listener on its own side,that waits for the Connection Request from the Client and make the Socket after Accepts the request.

Best Regards,
Lalit Narayan

Programm3r9-Dec-09 1:10

9-Dec-09 1:10

As far as my understanding of TCP/IP clients and server(s) goes; it is the client initiates the connection. So, if the client disconnect in any way from the server, when it is the clients 'responsibility' to reconnect to the server.

Kind regards,

The only programmers that are better C# programmers, are those who look like this -> Green Alien | [Alien]

Programm3r
My Blog: ^_^

lnmca9-Dec-09 1:14

9-Dec-09 1:14

Hi,
The Client Side Code is written in C at Embeded Side n it takes some time to show the status "Disconnected" this creates the problem 4 me,they find the state of Socket "Connected" while it is disconnected at Server Side...
Plz do the needful.

Thanks and Regards,
Lalit Narayam

Programm3r9-Dec-09 1:21

9-Dec-09 1:21

Well it seems to me that the embedded side needs some works?! Sniff | :^)

lnmca wrote:
The Client Side Code is written in C at Embeded Side n it takes some time to show the status "Disconnected" this creates the problem 4 me,they find the state of Socket "Connected" while it is disconnected at Server Side

You cannot build on something if it is not working correctly.. Dead | X|

The only programmers that are better C# programmers, are those who look like this -> Green Alien | [Alien]

Programm3r
My Blog: ^_^

Muhammad Bilal Saleem Barkati

Paulo Zemek9-Dec-09 2:31

Paulo Zemek

9-Dec-09 2:31

Well, I think you can't do that.
Imagine the situation:

Server starts reading.
Client starts sending. But, for some reason, the connection is VERY slow.
Server then receives the time-out (imagine it does not disconnect).
The server then asks for more data... but, the client is still sending the old-data. So, the server must now wait for what? The old data? The new data? How will it differentiate one data from the other?

I think the fact the connection is closed is on purpose. If you want, I think you may NOT use the ReceiveTimeOut. Instead, create another thread to call "abort" in the reading thread if it takes too long, so the connection will not be aborted, but I don't really know what will happen with the data in this case.

Also, depending on your requirements, it's possible to use UDP to receive the data.

error in 'if'

Muhammad Bilal Saleem Barkati8-Dec-09 23:33

8-Dec-09 23:33

is it a problem of my compiler?

if(((1*1*1)+(64*64*64))==(1*1*1))
        printf("my name");

the printf()is printing "my name".

N a v a n e e t h8-Dec-09 23:42

N a v a n e e t h

8-Dec-09 23:42

What compiler are you using? I tried with GCC and MSVC. printf is not executing in both places.

BTW, you are on a wrong forum.

Best wishes,
Navaneeth

Luc Pattyn8-Dec-09 23:47

Luc Pattyn

8-Dec-09 23:47

this does not look like C# code (printf is a C function); if your environment is using 16-bit arithmetic, then 64*64*64 would overflow as it equals 2^18

Smile | :)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]

I only read code that is properly indented, and rendered in a non-proportional font; hint: use PRE tags in forum messages

N a v a n e e t h8-Dec-09 23:56

N a v a n e e t h

8-Dec-09 23:56

I had a similar thought. But will it error out when overflow happens?

Best wishes,
Navaneeth