How to ensure the triggered jobs are rescheduled after the AppDomain recycle in Kudu, or to make an http request on recycles

We are using Kudu as a standalone installation, to manage all the IIS applications. But after the AppDomain or AppPool get recycled, all triggered jobs are rescheduled only after the next http request. The AppPool has been configured as "AlwaysRunning", and also "Preload" was enabled for the sites.

As possible workaround I can imagine, to fire an http request on AppDomain/Pool recycle, but how this can be achieved on IIS Configuration level, without modifying the Kudu sources?

Thank you.

0 Answers

If You Enjoyed This, Take 5 Seconds To Share It

• Facebook
• Twitter
• Google+
• StumbleUpon
• Digg
• Delicious
• LinkedIn
• Reddit
• Technorati