I see this mentioned in a few other posts, but none of them have a suitable solution.
I'm also discussing this via email with Kentico but thought I'd open it up on here too.
Background info... running Kentico 4.1 latest build, on a Win 2008 OS with IIS7 and SQL Server 2005 - all latest patches applied. Only 1 site on the entire box with 4GB ram.
The error in the Kentico log is:
EventType: E
EventTime: 12/16/2009 4:39:38 PM
Source: Application_End
EventCode: EXCEPTION
EventDescription: Message: HostingEnvironment initiated shutdown
HostingEnvironment caused shutdown<br />
Shutdown stack: at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
at System.Environment.get_StackTrace()
at System.Web.Hosting.HostingEnvironment.InitiateShutdownInternal()
at System.Web.Hosting.HostingEnvironment.InitiateShutdown()
at System.Web.Hosting.PipelineRuntime.StopProcessing()<br />
Call stack: at Global.LogApplicationEnd()
at Global.Application_End(Object sender, EventArgs e)
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Web.HttpApplication.ProcessSpecialRequest(HttpContext context, MethodInfo method, Int32 paramCount, Object eventSource, EventArgs eventArgs, HttpSessionState session)
at System.Web.HttpApplicationFactory.FireApplicationOnEnd()
at System.Web.HttpApplicationFactory.Dispose()
at System.Web.HttpRuntime.Dispose()
at System.Web.HttpRuntime.ReleaseResourcesAndUnloadAppDomain(Object state)
at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
We typically get one of two types of errors on the windows system log:
The worker processes serving application pool 'xyz.com(domain)(2.0)(pool)' are being recycled due to 1 or more configuration changes in the application pool properties which necessitate a restart of the processes.
A worker process with process id of '4796' serving application pool 'xyz.com(domain)(2.0)(pool)' has requested a recycle because it reached its virtual memory limit.
I'm not sure why there are any 'configuration changes', or why the worker process should reach a 4GB limit - not ever.
Would be great to hear any feedback or from people with similar problems.
James