Re: Problem with C# asynchronous sockets
- From: "christian.benien@xxxxxxxxx" <christian.benien@xxxxxxxxx>
- Date: 3 Oct 2005 10:46:05 -0700
Maybe some other part of your application takes away all your thread
pool threads, and there's none left to handle the socket operation. I
had that problem which caused by a bad System.Threading.Timer callback
method that waited infinitely on some lock.
Another idea is to monitor CLR performance counters for weird
behaviour, including the garbage collector (.NET CLR Memory)
.
- Follow-Ups:
- Re: Problem with C# asynchronous sockets
- From: Kruz
- Re: Problem with C# asynchronous sockets
- References:
- Problem with C# asynchronous sockets
- From: Kruz
- Re: Problem with C# asynchronous sockets
- From: Robert Jordan
- Re: Problem with C# asynchronous sockets
- From: Kruz
- Problem with C# asynchronous sockets
- Prev by Date: Cannot find member name System.Data.SqlClient.SqlError
- Next by Date: Re: Problem with C# asynchronous sockets
- Previous by thread: Re: Problem with C# asynchronous sockets
- Next by thread: Re: Problem with C# asynchronous sockets
- Index(es):