Hi, Anthony.
If you are able to reach your app once in a while, then no other app is using the port. To find our what happens we would have to know what exactly happens when you are unable to reach the server: does it time out, do you get "server refused the connection". Also, do you have clients on other machines hitting the server? The reason we are asking is because XP Home allows very limited number of incoming connections. As for the memory usage, we tested Cassini very extensively to ensure that it does not leak the memory. Whenever Cassini gets high memory usage, it was invariably some application, all of which are loaded into Cassini's process. Please note that if you registered your app with "keep it in memory" flag, it will cause your default page get hit every few minutes. Sometimes it causes lots of CPU usage and memory allocations, if the default page has lots of code. To see whether Cassini runs up memory, consider unregistering your app and let only Cassini service and Cassini Explorer run on their own, and see whether you get high memory usage too. Something to keep in mind is that Cassini does not force garbage collection, so it's up to .NET Framework to clean up memory. The only truly bad scenario is when memory usage goes only up. Also, please check Windows Event Log to see whether you see and errors related to UltiDev Cassini.
Please let us know if you get some more insights into high memory usage and possible reasons for service not responding.
Best regards,
UltiDev Team.
Please donate at
http://www.ultidev.com/products/Donate.aspx to help us improve our products.