Unblock NetworkStream.R ead from another Thread?

Dave,

I don't understand why you are looping infinitely. Why not use the
BeginAcceptTcpC lient and BeginRead methods to perform your work? You
wouldn't have to block a thread and poll. You would just be notified when
the client is available, and when your read was complete.

It would also use less resources, since you would be using I/O
completion ports (under the wrappers) instead of tying up a thread.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m

"DaveR" <NOSPAM_drubin@ NOSPAM_i-2000.com> wrote in message
news:Pa******** *************** ***@4ax.com...

I have a background thread to accept and process TCP/IP connections.
When the application shuts down I want to gracefully terminate it.

The thread will block in NetworkStream.R ead() waiting for data. I
expected that shutting down the TcpListener would unblock the Read()
and cause an exception, or return 0 bytes. But it does not work.

Relevant parts of the code are shown below. If a client connects, the
stream blocks in its Read() method. If Stop() is then called from the
main thread, NetworkStream.R ead() stays blocked even though the
TcpListener has stopped (and thus the underlying socket is closed).

I expect Read() to throw an IOException with an inner SocketException ,
or at least for it to unblock and return 0 bytes. But it doesn't work.

Any suggestions would be appreciated.

private TcpListener _listener;
public void StartListening( )
{
_listener = new TcpListener(end Point);
_listener.Start ();
Thread thread = new Thread(new ThreadStart(thi s.Process));
thread.Start();
}

public void StopListening()
{
_listener.Stop( );
}

private void Process()
{
while (true)
{
try
{
TcpClient client = _listener.Accep tTcpClient();
NetworkStream strm = client.GetStrea m();
while (true)
{
int bytesRead = strm.Read(buf, 0, buf.Length);
// ... process ...
}
}
catch (IOException e)
{
// Expect a SocketException when the listener stops
}
}
}

"DaveR" <NOSPAM_drubin@ NOSPAM_i-2000.com> wrote in message
news:Pa******** *************** ***@4ax.com...

I have a background thread to accept and process TCP/IP connections.
When the application shuts down I want to gracefully terminate it.

The thread will block in NetworkStream.R ead() waiting for data. I
expected that shutting down the TcpListener would unblock the Read()
and cause an exception, or return 0 bytes. But it does not work. .... private void Process()
{
while (true)
{
try
{
TcpClient client = _listener.Accep tTcpClient();
NetworkStream strm = client.GetStrea m();
while (true)
{
int bytesRead = strm.Read(buf, 0, buf.Length);
// ... process ...
}
}
catch (IOException e)
{
// Expect a SocketException when the listener stops
}
}
}

First, you are blocking accept while processing. When accept returns, you
should start new thread and process accepted connection on that thread. In
current implementation, you will not be able to process more than one
connection at the time.

To stop blocking read on TcpClient, you have to close tcpclient returned
from Accept, not listener. These two are unrelated. For that, you'll
probably have to track accepted connection (and remove them when they
disconnect).

Goran

The listener socket is seperate from the accepted socket (i.e. two different
objects). Stopping the listener, just stops the listener, not all
connected sockets. To shutdown connected sockets, you would need to walk a
list and close each one. hth

--
William Stacey [MVP]

"DaveR" <NOSPAM_drubin@ NOSPAM_i-2000.com> wrote in message
news:Pa******** *************** ***@4ax.com...
|I have a background thread to accept and process TCP/IP connections.
| When the application shuts down I want to gracefully terminate it.
|
| The thread will block in NetworkStream.R ead() waiting for data. I
| expected that shutting down the TcpListener would unblock the Read()
| and cause an exception, or return 0 bytes. But it does not work.
|
| Relevant parts of the code are shown below. If a client connects, the
| stream blocks in its Read() method. If Stop() is then called from the
| main thread, NetworkStream.R ead() stays blocked even though the
| TcpListener has stopped (and thus the underlying socket is closed).
|
| I expect Read() to throw an IOException with an inner SocketException ,
| or at least for it to unblock and return 0 bytes. But it doesn't work.
|
| Any suggestions would be appreciated.
|
| private TcpListener _listener;
| public void StartListening( )
| {
| _listener = new TcpListener(end Point);
| _listener.Start ();
| Thread thread = new Thread(new ThreadStart(thi s.Process));
| thread.Start();
| }
|
| public void StopListening()
| {
| _listener.Stop( );
| }
|
| private void Process()
| {
| while (true)
| {
| try
| {
| TcpClient client = _listener.Accep tTcpClient();
| NetworkStream strm = client.GetStrea m();
| while (true)
| {
| int bytesRead = strm.Read(buf, 0, buf.Length);
| // ... process ...
| }
| }
| catch (IOException e)
| {
| // Expect a SocketException when the listener stops
| }
| }
| }

On Tue, 30 May 2006 16:44:16 -0400, "Nicholas Paldino [.NET/C# MVP]"
<mv*@spam.guard .caspershouse.c om> wrote:

I don't understand why you are looping infinitely. Why not use the
BeginAcceptTcp Client and BeginRead methods to perform your work?

I have used that before in a server that needed to process many
simultaneous connections, but in this case we need to handle only a
single connection at a time, so I thought the asynchronous operation
may be overkill. Maybe that was not a wise choice.

In any case, I solved the problem by making the TcpClient a member and
closing it from the main thread, which effectively unblocks the
NetworkStream.R ead as I wanted.