July 11th, 2013, 01:40 AM
Sockets dying with heavy memory use
I have an app that runs a server (CLI) on a Windows 2008 Server. It runs a standard listen socket with max sockets and works great until someone uses a large number of system resources (Remote Desktop in, Team Source Explorer, etc.). Then the app stops responding on the port, but still is running. I can run it as either a Windows Service or as a Console App, but the problem is still there. Sometimes it calls the accept() then dies right away.
Anyone with any ideas why this is happening? This is a license server for a product, and we cannot have this dying all of the time.
Click Here to Expand Forum to Full Width