ApplicationInitialization not executing when using InProcess

[cannehag]

We have been using Application Initialization in our services to warm up the application before swapping slots (Azure App Services). We are using AppInsights for logging and have seen there initialization requests beeing logged with User-Agent "IIS Application Initialization Warmup".
When switching to InProcess hosting, these logs are missing.

<system.webServer>
      <applicationInitialization doAppInitAfterRestart="true" skipManagedModules="true">
         <add initializationPage="/api/heartbeat?checkDependencies=true" />
      </applicationInitialization>
</system.webServer>

Regardless of InProcess or not, Application Initialization should be executed.

[cannehag]

@muratg Any update on this? This is kind of serious since when using swapping in Azure, it will swap over to the production slot before the application is completely initialized.

[muratg]

@pakrym @jkotalik any thoughts here? Is this due to how logs are processed, or are we actually skipping this in InProc?

[pakrym]

We had a fix for AppInit in 3.0 #7024 which might help this.

[pakrym]

@cannehag are you able to try 3.0 preview using the site extension as described in https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/azure-apps/?view=aspnetcore-2.2#deploy-aspnet-core-preview-release-to-azure-app-service

[cannehag]

@pakrym Just tested and I can't really see it working. There is a request with User-Agent "SiteWarmup" executing. This is the build-in warmup targeting the root of the site. The applicationInitialization from web.config (which uses User-Agent "IIS Application Initialization Warmup") still doesn't run according to my logs.

How I tested:

• Creating a deployment slot
• Installed "ASP.NET Core 3.0 (x64) Runtime" extension on the slot
• Restarted slot
• Deployed application (with AppInit in web.config) and InProc hosting
• Swapped slots
• Verified in AppInsights that no "IIS Application Initialization Warmup" entries was found

[analogrelay]

@cannehag Can you try a self-contained deployment of 3.0? Also, I might suggest checking and logging the user agent in the app itself, rather than using App Insights, just to make sure you know if it's coming in. We have tests that seem to indicate this is working, so I want to make sure we know for sure what could be different in your environment :).

[analogrelay]

Closing this as we haven't heard from you and generally close issues with no response after some time. Please feel free to comment if you're able to get the information we're looking for and we can reopen the issue to investigate further!

[pseabury]

I'd like this reopened if possible per https://stackoverflow.com/questions/57679221/asp-net-core-2-2-site-warmup

Warmup doesn't seem to work with in-process hosting.

[Indigo744]

Please reopen this issue. App initialization is not working.

@anurse self-contained deployment does not help.

Please ignore the previous message. After some more testing, the issue was because only Windows Authentification was activated. App Initialization needs Anonymous auth.