roburst network programming, tcpClient.Clien t.SetSocketOpti on(SocketOption Level.Tcp , SocketOptionNam e.KeepAlive , 1);

[Ryan Liu]

Hi,

I use

Server:
Use an endless thread to lisiten to clients requests:

while(true)
{
TcpClient client = myListener.Acce ptTcpClient();
....
}
Client:
tcpClient = new TcpClient(host, port);
stream =tcpClient.GetS tream();
....
to build a client/server application, then both server and clients start
another endless thread to receive messages from each other, and use yet
other threads to send response to each other, or server pass messages from
one client to another.

Now about 60 workstations connect to one server, all in the same local LAN.

It is very ofter on server side log I see network problem for both read and
write to network stream, like:

Unable to write data to the transport connection.
An established connection was aborted by the software in your host machine.

Read System.InvalidO perationExcepti on: Operation not allowed on
non-connected sockets.

Can someone tell me what will cause the problem and how to write a roburst
network application?

I am using TcpClient, in SDK, I see there is a method

Socket.SetSocke tOption(), which can set SocketOptionNam e.KeepAlive

What does this mean, will this be helpful?

And do I have set this on both client and server side? And is this the right
way to use it:
tcpClient.Clien t.SetSocketOpti on(SocketOption Level.Tcp ,
SocketOptionNam e.KeepAlive , 1);

Thanks a lot!
Ryan

[chanmm]

Hope this will somehow help you but it is in VB.NET.
http://msdn.microsoft.com/library/de...et10232001.asp

chanmm

"Ryan Liu" <ad********@onl ine.sh.cnwrote in message
news:un******** ******@TK2MSFTN GP04.phx.gbl...

Hi,

I use

Server:
Use an endless thread to lisiten to clients requests:

while(true)
{
TcpClient client = myListener.Acce ptTcpClient();
....
}
Client:
tcpClient = new TcpClient(host, port);
stream =tcpClient.GetS tream();
....
to build a client/server application, then both server and clients start
another endless thread to receive messages from each other, and use yet
other threads to send response to each other, or server pass messages from
one client to another.

Now about 60 workstations connect to one server, all in the same local
LAN.

It is very ofter on server side log I see network problem for both read
and
write to network stream, like:

Unable to write data to the transport connection.
An established connection was aborted by the software in your host
machine.

Read System.InvalidO perationExcepti on: Operation not allowed on
non-connected sockets.

Can someone tell me what will cause the problem and how to write a roburst
network application?

I am using TcpClient, in SDK, I see there is a method

Socket.SetSocke tOption(), which can set SocketOptionNam e.KeepAlive

What does this mean, will this be helpful?

And do I have set this on both client and server side? And is this the
right
way to use it:
tcpClient.Clien t.SetSocketOpti on(SocketOption Level.Tcp ,
SocketOptionNam e.KeepAlive , 1);

Thanks a lot!
Ryan

[Markus Stoeger]

Ryan Liu wrote:

It is very ofter on server side log I see network problem for both read and
write to network stream, like:

Unable to write data to the transport connection.
An established connection was aborted by the software in your host machine.

Read System.InvalidO perationExcepti on: Operation not allowed on
non-connected sockets.

Can someone tell me what will cause the problem and how to write a roburst
network application?

I am using TcpClient, in SDK, I see there is a method

Socket.SetSocke tOption(), which can set SocketOptionNam e.KeepAlive

What does this mean, will this be helpful?

I don't think KeepAlives will help you (see google). You are getting the
error because you are writing to a socket whose connection has been
closed (either intentionally or because of other reasons like network
problems or a crashed server).

When calling Socket.Receive you should 1) use a try/catch block around
it and 2) check the return value. A return value of 0 means that the
connection has been closed. You should not call Send on the socket after
it returned 0 bytes or after an exception. Close and destroy it.

btw - why not use async sockets instead of starting so many threads?

hth,
Max

[Ryan Liu]

Hi Markus,

Actually I have no problem with Listener, I have problem after the
connection is made. Then the server spawn one thread for each connected
client.

Actually there is not lot of threads. Only one thread for server to listen,
and one thread in server to receive data from each client and handle it.

When one client send message to server then server pass to another client,
it only involves one thread of the first client, but 2 network streams.

Thanks,
Ryan


"Markus Stoeger" <sp******@gmx.a t????
news:e1******** ********@TK2MSF TNGP03.phx.gbl. ..

Ryan Liu wrote:

It is very ofter on server side log I see network problem for both read

and

write to network stream, like:

Unable to write data to the transport connection.
An established connection was aborted by the software in your host

machine.

Read System.InvalidO perationExcepti on: Operation not allowed on
non-connected sockets.

Can someone tell me what will cause the problem and how to write a

roburst

network application?

I am using TcpClient, in SDK, I see there is a method

Socket.SetSocke tOption(), which can set SocketOptionNam e.KeepAlive

What does this mean, will this be helpful?

I don't think KeepAlives will help you (see google). You are getting the
error because you are writing to a socket whose connection has been
closed (either intentionally or because of other reasons like network
problems or a crashed server).

When calling Socket.Receive you should 1) use a try/catch block around
it and 2) check the return value. A return value of 0 means that the
connection has been closed. You should not call Send on the socket after
it returned 0 bytes or after an exception. Close and destroy it.

btw - why not use async sockets instead of starting so many threads?

hth,
Max