Dotnetnuke "keepalive"

Question

I have several DNN portals that I manage, and I need a solution so that they are alive during slow traffic. After a specified period of inactivity, IIS will unload the DNN application from memory, which will affect the load time for the first client request. DNN has a file called "KeepAlive.aspx" that I hit with the wget command from the CRON job every 5 minutes. I doubt the effectiveness of this method. Anyone have any other ideas?

Answer 1

A good website monitoring service is likely to provide you with a URL to check if the site is working, what the Keepalive URL is for. Ask the service to check the URL more often than 15 minutes and you should be good to go with saving the site. There is always a chance that the site will go on some other problem, but the keep alive service should return it if this happens, and the other user has not hit it yet.

Answer 2

In the launch event of the global application, you can configure a cache element or timer with a timeout of 5 minutes, and in the callback code, ping a simple page that should return an HTTP 200 - reset cache / timer, and repeat.

Answer 3

, ,

• Host-Tracker
• Pingdom
• KeepAliveForever

Host-Tracker Pingdom, ,