The site starts slowly but it is fine once it is up
Hi,
I am new to Umbraco and built a new website in Umbraco.
My team is very happy now that they can change content of website however when Umbraco loads initially it takes a lot of time. Don't understand the reason for it.I did some googling and found that it may because of inactivity of website in IIS or some articles are pointing that it may be examine indexes.
Please help me with your professional guidance what should I do to mitigate this issue.
Details of setup:
Windows server 2012R2
Webserver IIS 8.0
Umbraco version (7.7.6)
URL tracker is enabled by default in backoffice (no idea what it is)
Umbraco generic property is added on home content node to redirect to another page.
<add key="Umbraco.ModelsBuilder.ModelsMode" value="PureLive" /> in webconfig.
I am using URL redirect module in IIS to redirect pages to new Umbraco pages.Basically I am hosting two website on IIS one Umbraco and other one is static website (our old website) our old website is still active if some users have bookmarked(i.e about.aspx) old website pages - URL redirect module is redirecting to Umbraco pages(i.e aboutus/).
Tested Umbraco website locally - site loads completely fine.
log:
_shutDownMessage=HostingEnvironment initiated shutdown
HostingEnvironment caused shutdown
_shutDownStack= at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
at System.Environment.get_StackTrace()
at System.Web.Hosting.HostingEnvironment.InitiateShutdownInternal()
at System.Web.Hosting.PipelineRuntime.StopProcessing()
2017-12-14 13:03:25,912 [P9916/D2/T1] INFO Umbraco.Core.CoreBootManager - Umbraco 7.7.6 application starting on W-AB
2017-12-14 13:03:25,959 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Determining hash of code files on disk
2017-12-14 13:03:26,006 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Hash determined (took 38ms)
2017-12-14 13:03:26,099 [P9916/D2/T1] INFO Umbraco.Core.MainDom - Acquiring MainDom...
2017-12-14 13:03:26,099 [P9916/D2/T1] INFO Umbraco.Core.MainDom - Acquired MainDom.
2017-12-14 13:03:26,099 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IDiscoverable
2017-12-14 13:03:26,240 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IDiscoverable (took 134ms)
2017-12-14 13:03:26,240 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IApplicationStartupHandler
2017-12-14 13:03:26,240 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IApplicationStartupHandler (took 2ms)
2017-12-14 13:03:26,334 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IDiscoverable
2017-12-14 13:03:26,334 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IDiscoverable (took 1ms)
2017-12-14 13:03:26,334 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Resolving Umbraco.Core.PropertyEditors.IPropertyEditorValueConverter
2017-12-14 13:03:26,334 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Resolved Umbraco.Core.PropertyEditors.IPropertyEditorValueConverter (took 0ms)
2017-12-14 13:03:26,334 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IDiscoverable
2017-12-14 13:03:26,334 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IDiscoverable (took 0ms)
2017-12-14 13:03:26,334 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Resolving Umbraco.Core.PropertyEditors.IPropertyValueConverter
2017-12-14 13:03:26,349 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Resolved Umbraco.Core.PropertyEditors.IPropertyValueConverter (took 5ms)
2017-12-14 13:03:26,365 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IDiscoverable
2017-12-14 13:03:26,365 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IDiscoverable (took 0ms)
2017-12-14 13:03:26,365 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Resolving Umbraco.Web.Mvc.SurfaceController
2017-12-14 13:03:26,365 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Resolved Umbraco.Web.Mvc.SurfaceController (took 0ms)
2017-12-14 13:03:26,365 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IDiscoverable
2017-12-14 13:03:26,365 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IDiscoverable (took 0ms)
2017-12-14 13:03:26,365 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Resolving Umbraco.Web.WebApi.UmbracoApiController
2017-12-14 13:03:26,365 [P9916/D2/T1] INFO Umbraco.Core.PluginManager - Resolved Umbraco.Web.WebApi.UmbracoApiController (took 1ms)
2017-12-14 13:03:32,818 [P9916/D2/T1] INFO Umbraco.Core.DatabaseContext - CanConnect = True
2017-12-14 13:03:33,490 [P9916/D2/T1] INFO Umbraco.Web.Cache.CacheRefresherEventHandler - Initializing Umbraco internal event handlers for cache refreshing
2017-12-14 13:03:33,959 [P9916/D2/T1] INFO Umbraco.Web.Search.ExamineEvents - Initializing Examine and binding to business logic events
2017-12-14 13:03:33,959 [P9916/D2/T1] INFO Umbraco.Web.Search.ExamineEvents - Adding examine event handlers for index providers: 3
2017-12-14 13:03:34,193 [P9916/D2/T1] INFO Umbraco.Core.CoreBootManager - Umbraco application startup complete (took 8558ms)
2017-12-14 13:03:35,256 [P9916/D2/T12] INFO Umbraco.Core.Sync.ApplicationUrlHelper - ApplicationUrl: http://ab.ab.org:80/umbraco (UmbracoModule request)
2017-12-14 13:03:36,037 [P9916/D2/T12] INFO umbraco.content - Load Xml from file...
2017-12-14 13:03:36,052 [P9916/D2/T12] INFO umbraco.content - Loaded Xml from file.
2017-12-14 13:03:37,693 [P9916/D2/T12] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IDiscoverable
2017-12-14 13:03:37,693 [P9916/D2/T12] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IDiscoverable (took 0ms)
2017-12-14 13:03:37,693 [P9916/D2/T12] INFO Umbraco.Core.PluginManager - Resolving Umbraco.Core.PropertyEditors.IParameterEditor
2017-12-14 13:03:37,693 [P9916/D2/T12] INFO Umbraco.Core.PluginManager - Resolved Umbraco.Core.PropertyEditors.IParameterEditor (took 1ms)
2017-12-14 13:03:48,865 [P9916/D2/T12] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IDiscoverable
2017-12-14 13:03:48,865 [P9916/D2/T12] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IDiscoverable (took 0ms)
2017-12-14 13:03:48,865 [P9916/D2/T12] INFO Umbraco.Core.PluginManager - Resolving [Umbraco.Web.Trees.TreeAttribute]Umbraco.Web.Trees.TreeController
2017-12-14 13:03:48,865 [P9916/D2/T12] INFO Umbraco.Core.PluginManager - Resolved [Umbraco.Web.Trees.TreeAttribute]Umbraco.Web.Trees.TreeController (took 0ms)
2017-12-14 13:03:53,396 [P9916/D2/T13] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IDiscoverable
2017-12-14 13:03:53,396 [P9916/D2/T13] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IDiscoverable (took 0ms)
2017-12-14 13:03:53,396 [P9916/D2/T13] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IAction
2017-12-14 13:03:53,396 [P9916/D2/T13] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IAction (took 1ms)
2017-12-14 13:04:36,130 [P9916/D2/T8] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IDiscoverable
2017-12-14 13:04:36,130 [P9916/D2/T8] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IDiscoverable (took 0ms)
2017-12-14 13:04:36,130 [P9916/D2/T8] INFO Umbraco.Core.PluginManager - Resolving [Umbraco.Core.Persistence.Mappers.MapperForAttribute]Umbraco.Core.Persistence.Mappers.BaseMapper
2017-12-14 13:04:36,130 [P9916/D2/T8] INFO Umbraco.Core.PluginManager - Resolved [Umbraco.Core.Persistence.Mappers.MapperForAttribute]Umbraco.Core.Persistence.Mappers.BaseMapper (took 1ms)
2017-12-14 13:04:36,255 [P9916/D2/T13] INFO umbraco.BusinessLogic.Log - Log scrubbed. Removed all items older than 2017-12-13 13:04:36
2017-12-14 13:04:37,239 [P9916/D2/T6] ERROR Umbraco.Web.Scheduling.KeepAlive - Failed (at "http://ab.ab.org:80/umbraco").
System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 172.21.211.15:80
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
--- End of inner exception stack trace ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Umbraco.Web.Scheduling.KeepAlive.<PerformRunAsync>d__4.MoveNext()
2017-12-14 13:09:38,267 [P9916/D2/T38] ERROR Umbraco.Web.Scheduling.KeepAlive - Failed (at "http://ab.ab.org:80/umbraco").
System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 172.21.211
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
--- End of inner exception stack trace ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Umbraco.Web.Scheduling.KeepAlive.<PerformRunAsync>d__4.MoveNext()
I had this issue with a site I made. I changed from using the PureLive to typed models - which made a huge difference.
Normally the IIS-application pool shuts down to idling after 20 minutes of inactivity - with some(?) versions of IIS you can change that setting, it's not good to have it indefinetly but I usually put mine on 60-180 minutes.
The site starts slowly but it is fine once it is up
Hi,
I am new to Umbraco and built a new website in Umbraco. My team is very happy now that they can change content of website however when Umbraco loads initially it takes a lot of time. Don't understand the reason for it.I did some googling and found that it may because of inactivity of website in IIS or some articles are pointing that it may be examine indexes.
Please help me with your professional guidance what should I do to mitigate this issue.
Details of setup:
<add key="Umbraco.ModelsBuilder.ModelsMode" value="PureLive" />
in webconfig.log:
Hi Usman
Are you using Umbraco events for reindexing Examine indexes on the start or something like that?
THanks,
Alex
I had this issue with a site I made. I changed from using the PureLive to typed models - which made a huge difference.
Normally the IIS-application pool shuts down to idling after 20 minutes of inactivity - with some(?) versions of IIS you can change that setting, it's not good to have it indefinetly but I usually put mine on 60-180 minutes.
is working on a reply...