We started seeing behavior in environments that are causing a runtime exception when trying to navigate to backoffice. Our delivery servers are still serving content. The stack trace is as follows:
2017-07-18 11:24:44,476 [P25320/D55/T14] ERROR Umbraco.Core.CoreBootManager - An error occurred running OnApplicationStarting for handler MyOrg.Application.Core.CoreExtension.ApplicationAppEventHandler
System.InvalidOperationException: Type MyOrg.Application.Core.CoreExtension.ApplicationContentFinder is already in the collection of types.
at Umbraco.Core.ObjectResolution.ManyObjectsResolverBase`2.InsertTypeBefore(Type existingType, Type value)
at MyOrg.Application.Core.CoreExtension.ApplicationAppEventHandler.ApplicationStarting(UmbracoApplicationBase umbracoApplication, ApplicationContext applicationContext) in F:\TeamCityBuildAgent\BuildAgent\work\c6e8f5976b5b4087\MyOrg.Application.Core\CoreExtension\ApplicationAppEventHandler.cs:line 18
at Umbraco.Core.ApplicationEventHandler.OnApplicationStarting(UmbracoApplicationBase umbracoApplication, ApplicationContext applicationContext)
at Umbraco.Core.CoreBootManager.<Startup>b__8(IApplicationEventHandler x)
2017-07-18 11:24:44,476 [P25320/D55/T14] ERROR Umbraco.Core.UmbracoApplicationBase - An unhandled exception occurred
System.InvalidOperationException: Type MyOrg.Application.Core.CoreExtension.ApplicationContentFinder is already in the collection of types.
at Umbraco.Core.ObjectResolution.ManyObjectsResolverBase`2.InsertTypeBefore(Type existingType, Type value)
at MyOrg.Application.Core.CoreExtension.ApplicationAppEventHandler.ApplicationStarting(UmbracoApplicationBase umbracoApplication, ApplicationContext applicationContext) in F:\TeamCityBuildAgent\BuildAgent\work\c6e8f5976b5b4087\MyOrg.Application.Core\CoreExtension\ApplicationAppEventHandler.cs:line 18
at Umbraco.Core.ApplicationEventHandler.OnApplicationStarting(UmbracoApplicationBase umbracoApplication, ApplicationContext applicationContext)
at Umbraco.Core.CoreBootManager.<Startup>b__8(IApplicationEventHandler x)
at Umbraco.Core.EnumerableExtensions.ForEach[TItem](IEnumerable`1 items, Action`1 action)
at Umbraco.Core.CoreBootManager.Startup(Action`1 afterStartup)
at Umbraco.Core.UmbracoApplicationBase.StartApplication(Object sender, EventArgs e)
After some investigation, we discovered the root issue to be the umbraco-plugins.{machinename}.list. Deleting this file and letting it regenerate allows for a temporary fix, however the problem seems to return after an indeterminate amount of time.
It seems as if this file was duplicating some of the line items after a seemingly random amount of time (potentially after a period of inactivity?). The file's duplicated entries are as follows:
There are additional entries in this file that are not being duplicated which include items that live in Umbraco.Web.
Does anyone know what triggers these files to be regenerated and what could possibly be causing this to affect some of our environments but not others? Any information would be appreciated. Our current version is 7.5.9.
For what it's worth, in looking at the Umbraco source, it seems the offending code (PluginManager.cs) has been updated in subsequent minor releases, so upgrading is certainly on the table if it would fix this problem.
Duplicate entries in umbraco-plugins.{machinename}.list on Application Starting
We started seeing behavior in environments that are causing a runtime exception when trying to navigate to backoffice. Our delivery servers are still serving content. The stack trace is as follows:
After some investigation, we discovered the root issue to be the umbraco-plugins.{machinename}.list. Deleting this file and letting it regenerate allows for a temporary fix, however the problem seems to return after an indeterminate amount of time.
It seems as if this file was duplicating some of the line items after a seemingly random amount of time (potentially after a period of inactivity?). The file's duplicated entries are as follows:
There are additional entries in this file that are not being duplicated which include items that live in Umbraco.Web.
Does anyone know what triggers these files to be regenerated and what could possibly be causing this to affect some of our environments but not others? Any information would be appreciated. Our current version is 7.5.9.
For what it's worth, in looking at the Umbraco source, it seems the offending code (PluginManager.cs) has been updated in subsequent minor releases, so upgrading is certainly on the table if it would fix this problem.
is working on a reply...