应用程序域在节点发布时重新启动 - Umbraco答案

【问题标题】：Application domain restarts on node publish - Umbraco应用程序域在节点发布时重新启动 - Umbraco
【发布时间】：2016-06-14 22:32:36
【问题描述】：

每当我在 Umbraco 6.2.5 上发布节点时，应用程序域都会重新启动。

日志显示：应用程序关闭。原因：配置更改

在发布期间修改的唯一文件在 App_Data 中：Umbraco.config 和 TEMP\ExamineIndexes 的内容。

我没有针对这些文件进行实时病毒扫描。关于如何防止这种情况的任何想法？ FCNMode = disabled 没有解决问题。

    2015-03-08 16:05:50,611 [15] INFO  Umbraco.Core.Publishing.PublishingStrategy - [Thread 7] Content 'test3' with Id '2292' has been published.
    2015-03-08 16:05:51,517 [20] INFO  Umbraco.Core.PluginManager - [Thread 11] Determining hash of code files on disk
    2015-03-08 16:05:51,533 [20] INFO  Umbraco.Core.PluginManager - [Thread 11] Hash determined (took 7ms)
    2015-03-08 16:05:51,549 [20] INFO  Umbraco.Core.PluginManager - [Thread 11] Starting resolution types of umbraco.interfaces.IApplicationStartupHandler
    2015-03-08 16:05:51,580 [20] INFO  Umbraco.Core.PluginManager - [Thread 11] Completed resolution of types of umbraco.interfaces.IApplicationStartupHandler, found 25 (took 26ms)
    2015-03-08 16:05:51,611 [20] INFO  Umbraco.Core.PluginManager - [Thread 11] Starting resolution types of Umbraco.Core.PropertyEditors.IPropertyEditorValueConverter
    2015-03-08 16:05:51,611 [20] INFO  Umbraco.Core.PluginManager - [Thread 11] Completed resolution of types of Umbraco.Core.PropertyEditors.IPropertyEditorValueConverter, found 0 (took 2ms)
    2015-03-08 16:05:51,611 [20] INFO  Umbraco.Core.PluginManager - [Thread 11] Starting resolution types of Umbraco.Core.PropertyEditors.IPropertyValueConverter
    2015-03-08 16:05:51,611 [20] INFO  Umbraco.Core.PluginManager - [Thread 11] Completed resolution of types of Umbraco.Core.PropertyEditors.IPropertyValueConverter, found 12 (took 0ms)
    2015-03-08 16:05:51,642 [20] INFO  Umbraco.Core.PluginManager - [Thread 11] Starting resolution types of Umbraco.Web.Mvc.SurfaceController
    2015-03-08 16:05:51,642 [20] INFO  Umbraco.Core.PluginManager - [Thread 11] Completed resolution of types of Umbraco.Web.Mvc.SurfaceController, found 5 (took 0ms)
    2015-03-08 16:05:51,642 [20] INFO  Umbraco.Core.PluginManager - [Thread 11] Starting resolution types of Umbraco.Web.WebApi.UmbracoApiController
    2015-03-08 16:05:51,642 [20] INFO  Umbraco.Core.PluginManager - [Thread 11] Completed resolution of types of Umbraco.Web.WebApi.UmbracoApiController, found 3 (took 0ms)
    2015-03-08 16:05:51,642 [20] INFO  Umbraco.Core.PluginManager - [Thread 11] Starting resolution types of Umbraco.Core.Media.IThumbnailProvider
    2015-03-08 16:05:51,642 [20] INFO  Umbraco.Core.PluginManager - [Thread 11] Completed resolution of types of Umbraco.Core.Media.IThumbnailProvider, found 3 (took 0ms)
    2015-03-08 16:05:51,642 [20] INFO  Umbraco.Core.PluginManager - [Thread 11] Starting resolution types of Umbraco.Core.Media.IImageUrlProvider
    2015-03-08 16:05:51,642 [20] INFO  Umbraco.Core.PluginManager - [Thread 11] Completed resolution of types of Umbraco.Core.Media.IImageUrlProvider, found 1 (took 0ms)
    2015-03-08 16:05:52,174 [20] INFO  Umbraco.Web.Search.ExamineEvents - [Thread 11] Initializing Examine and binding to business logic events
    2015-03-08 16:05:52,174 [20] INFO  Umbraco.Web.Search.ExamineEvents - [Thread 11] Adding examine event handlers for index providers: 3
    2015-03-08 16:05:52,314 [20] INFO  Umbraco.Web.UmbracoModule - [Thread 22] Setting OriginalRequestUrl: dev.foo.com:80/umbraco
    2015-03-08 16:05:52,486 [15] INFO  Umbraco.Core.UmbracoApplicationBase - [Thread 22] Application shutdown. Reason: ConfigurationChange

【问题讨论】：

标签： asp.net iis umbraco

【解决方案1】：

我们目前正在调查这个可能与 Microsoft KB3000850 补丁有关的问题。您能否确认在您开始遇到这些问题之前已安装此补丁？

【讨论】：

我可以确认去年 11 月在 Win 2012 x64 服务器上安装了 KB3000850。从那段时间开始，我没有方便的服务器日志，但应用程序在发布时重新启动似乎确实在那个时候开始出现。
好的，这有帮助。我会在这里报告我们的发现。
@sebastiaan 有这方面的消息吗？我们在这里遇到了同样的问题。 :(
更新：MS 确认这是由于包含在 KB3000850 - support.microsoft.com/en-us/kb/3007507 中的这个补丁 - 所以只需删除 KB3007507 就足够了。如果您想订阅电子邮件更新，问题在我们的跟踪器中：issues.umbraco.org/issue/U4-6338
MS 现已为此发布了一个公共补丁：support.microsoft.com/en-us/kb/3052480

【解决方案2】：

首先，我会删除 umbraco.config 并重新启动 apppol。

这也可能是权限问题吗？通过确保您的 apppol 用户对网站中的所有文件夹拥有完全权限来进行测试。

【讨论】：

感谢您的意见，但遗憾的是这并不能解决问题。我已验证网站运行的应用程序池身份对网站具有完全控制权限。任何 Web 文件的 WIndows 索引都被禁用，实时防病毒监控也是如此。 .