应用程序池回收和工作流程
在这种情况下，WF 4 WCF 工作流服务（xamlx）托管在 IIS 中，如何适应应用程序池可能随时回收这一事实（配置编辑、内存压力等）以及一个或多个 WCF 启动的工作流（当应用程序池被拆除并重新启动时，s) 可能仍在执行。令人担忧的是，工作流可能正在执行其活动，而 IIS 主机拆卸可能会阻止该线程（或线程，如果使用异步活动）完成并使工作流处于不稳定状态。我们可以为此使用事务范围或其他一些构造，但不确定整体行为，以便最好地规划如何适应它？
In this scenario, WF 4 WCF workflow service (xamlx's) hosted in IIS, how does one accomodate the fact that the app pool may be recycled at any time (config edit, memory pressure, etc.) and one or more WCF initiated workflow(s) may still be executing when the app pool is being torn down and restarted. The concern is that a workflow may be executing it's activities and the IIS host tear down may prevent that thread (or threads if async activities used) from completing and leave the workflow in an unstable state. We could use transaction scope or some other construct for this but not sure of the overall behavior in order to best plan on how to accomodate it?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
IIS 有一个称为“重叠回收”的功能，默认情况下启用该功能，导致以前的 AppPool 在完全销毁之前被授予一段时间。我相信这个功能是在 IIS 7.5 中首次引入的。您应该能够在应用程序池/高级设置/回收下找到它，我不记得确切的时间，但只要您没有进行大量计算，您应该没问题。
IIS has a feature called Overlapped Recycle that is enabled by default resulting in the previous AppPool being granted some time before it is completely destroyed. I believe this feature was first introduces in IIS 7.5. You should be able to find it under Application Pools/Advanced Settings/Recycling I don't recall the exact amount of time but providing you are not doing extensive computation you should be fine.