I have a service running on a shared Windows 2003 server. Every few weeks my process goes bonkers (goes to 100% CPU utilization). When this happens other services on the system start failing to work properly, or work incredibly slowly. Further (and far worse) I can no longer RDC into the box to kill and restart the process.
Thus far I've been unable to figure out what causes my process to freak out, but I'm still investigating it. Until I do, I need:
- To always be able to RDC into the machine.
- My process' behavior to not freak out the rest of the server.
So, is there a) a way to get my service to always run at lower priority, and b) a way to ensure that RDC is always able to connect (high priority)?
And as a random aside, should I not be surprised that Windows Server does not have better resource management to prevent one same-priority crazy process from destroying the entire server?
