|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Dot.Net Error -- any idea? "System.Net.Sockets.SocketException:"running on the same box (and Dot Net 1.1). We'll start our application, and it will make a TCP/IP connection to a host computer, but after a few hours, we'll see this error: "System.Net.Sockets.SocketException: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full" We found a KB article about if you have more than 50 protocols bound to multiple interfaces, then that could be the issue, but we are only running 1 Network connection, and only 1 protocol (TCP/IP). Any ideas? I would expect to see that if your socket receiver isn't pulling data out of
Windows quickly enough. If your server stops pulling data out of the buffer (your receive thread gets deadlocked or terminated, you forget to call BeginReceive, or some other related issue) then Windows will queue up data for a bit, then reject incoming data. This sounds to me like what you're seeing. -- Show quoteChris Mullins, MCSD.NET, MCPD:Enterprise, Microsoft C# MVP http://www.coversant.com/blogs/cmullins "Ringholz, Blake" <bringh***@Galvanon.com> wrote in message news:0002E833-E798-4F99-9E66-6B86EEA61FD9@microsoft.com... > We are running Windows Server 2003 Standard SP1 with both IIS and SQL2000 > running on the same box (and Dot Net 1.1). We'll start our application, > and it will make a TCP/IP connection to a host computer, but after a few > hours, we'll see this error: > > > > "System.Net.Sockets.SocketException: An operation on a socket could not be > performed because the system lacked sufficient buffer space or because a > queue was full" > > > > We found a KB article about if you have more than 50 protocols bound to > multiple interfaces, then that could be the issue, but we are only running > 1 Network connection, and only 1 protocol (TCP/IP). > > > > Any ideas? > |
|||||||||||||||||||||||