Is there something in the Web Connection Handler that will, based on some criteria, reset or reload comm servers daily / periodically?
The reason I ask is because I've an WC application that when run as a standard windows exe in file mode will seemingly run for months without interruption. When I run the same server in COM mode and monitor it via the Web Connection Handler Status Page I noticed that the server is being restarted daily (at different times but still daily). So I'm wondering if this is normal behavior or if I have an issue with my code? As a result of the reset the WC Handler Status Page shows the Process ID changed, the Hit Count is reset and the Stated indicator shows the Date - Time the process was Started.
Also, In an effort to do some load testing I've launched 3 com instances of the server, LoadBased. The 1st instance obviously gets a lot of hits, the 2nd instance gets a few hits and the 3rd instance has not gotten any hits. So clearly I don't need to run 3 instances of the server right now, when 2 instances will likely work just fine! What I find interesting is that when the com server reset occurs all 3 instances of the server are killed and restarted at the same time. Even the instance that does not receive any hits and is completely idle. That is why I'm wondering if the reset is just something that the WC does periodically, or if there is an issue in my code that I need to address.
Your Thoughts
IIS has a 20 minute idle timeout by default and will unload servers if the site has not gotten any hits for that timeout.
You can set that timeout value in the Application Pool configuration in IIS.
Servers will also restart when you make setting changes in web.config.
+++ Rick ---
Perfect, THANK YOU!
That explains the behavior and gives me confidence that my server is running without error.