Hi Rick, Hope you are well. I am trying to understand why my soap based web service is unavailable intermittently. First, I noticed if I do not stop and restart the service about every 2 weeks, it will simply be unaccessible. It has always been that way and it's not a big deal. I simply make it a point to do that. Been doing that for years. Sometimes I forget to do that and it is usually the next day before I am aware that none of the vendors were able to hit the service for the past 24 hours. So, I wrote a program that hits the service on localhost every hour and beeps me if it is unable to hit the service. That program is beeping me about once or twice a day. Looking at the IIS logs I see where a vendor hits the service via port 443 (https) every few minutes. I also see where the service appears to get hit every few seconds on port 80 (so localhost). My program is only doing that every hour so I am wondering if I am reading the log incorrectly or what is going on. Here is a recent log. Can you give me a better understanding of the numerous hits from localhost?
Not sure about the hits - that's something coming from your own tooling. Perhaps you have some other monitoring software running that is checking the server that you're forgetting about? Web Monitor perhaps?
As to the server recycling - you can force IIS to auto-recycle by setting the Auto-recycling in the application pool. I like to reset the server once every day for FoxPro servers. The recycling does this in a controlled manner shutting down the old pool and letting requests run out and then starting a new one. It's on by default, unless you turned it off. The default - oddly - is 1790 minutes (19 hours).
+++ Rick ---
Thanks Rick, No, I do not have Web Monitor but it looks like it may be an option. I will ask my cloud service provider if perhaps they have something running that may be causing this. Thanks for the education, John
If it's hitting your specific APIs then that's unlikely their monitoring would hit it.
If this server is on the open internet and accessible by anyone it could be anything. It could be bots, or it could be the client's application that's checking if your API is available.
You just have to live with that and make sure you don't provide data that shouldn't be with any request that's not properly authorized etc.
+++ Rick ---
