We're working on a project where we've built a large custom Web API that integrates into Umbraco. After a period of inactivity we're running into a problem where we can't access the API (0 NO RESPONSE) without hitting the Umbraco website first, it looks like hitting the API isn't enough for the Umbraco app to startup.
We've changed the Idle Time-out setting on IIS to 0, with the understanding that it will stop it going idle.
Is there something we are missing or need to configure elsewhere so that hitting the API alone will start the application?
Stop Umbraco going idle
Hi,
We're working on a project where we've built a large custom Web API that integrates into Umbraco. After a period of inactivity we're running into a problem where we can't access the API (0 NO RESPONSE) without hitting the Umbraco website first, it looks like hitting the API isn't enough for the Umbraco app to startup.
We've changed the Idle Time-out setting on IIS to 0, with the understanding that it will stop it going idle.
Is there something we are missing or need to configure elsewhere so that hitting the API alone will start the application?
Thanks in advance
Alex
Alex,
Does this help http://stackoverflow.com/questions/3891178/how-to-prevent-extend-idletimeout-in-iis-7
Regards
Ismail
Hi Ismail,
Thanks for finding this link for me. I've taken a look at it and I've set the idle timeout to 0, but still doesn't appear to be working.
Seems to be a strange one.
Here's my configuration in IIS.
is working on a reply...