Help with socket problem...

Aaron Dilliard

I have a server which updates programs on our local network, informs of notifications, etc... The problem is that after so long it will "lock up" and stop accepting connections. I have connected/disconnected clients and tested everywhere for a solution to the problem. There is actually a series of about 6 servers on different ports, and all of them quit accepting at once. The MainSocket is using Socket.BeginAccept and waiting for connections, then passes them off to a data structure I created to maintain the connections/user info/etc. Is there a certain period of "idle time" when the Framework aborts that thread? It seems like if that were the case, however, you wouldnt even be able to connect to the server. As it is, you can get a connection, you just cant communicate. I know without seeing the code it may be hard to determine a solution, but Im not sure exactly what the problem is. Any thoughts or comments would be appreciated... Aaron

Tom Wright

did you say that all disconnect or stop accepting connections at the same time? Have you tried running the server and client on your machine to see if they stay up and running? What about traping the socket errors are they reporting anything? T Tom Wright tawright915@yahoo.com

Aaron Dilliard

Yes, that is how I tested them to get the bugs out (On My Machine). It takes a good 2 days or so before they stop accepting connections, however, and debugging for that long really isnt feasible, because it doesnt always happen. It does report errors, but the error logs dont report anything unusual, client connected/disconnected, updating database, etc. Nothing that should clog the server like that. Thanks... Aaron

leppie

How are you running this? Windows service? ASP.NET? Windows app? Command line? Different/same PC? Maybe the hardware is going into power saving mode...

xacc.ide-0.1.3.2