尽管没有书签和挂起计时器，AppFabric/WF 4.0 实例仍然卡住 [英] AppFabric / WF 4.0 instances stuck despite no bookmark and pending timer

问题描述

我已经发布了一个关于此的问题(废弃的实例不会继续执行(僵尸实例))，但仍然没有得到答案.

I already posted a question about this (Abandoned instances that will not continue execution (zombie instances)), but still haven't got an answer.

我从上一个问题中注意到的一个区别是，当未处理异常的服务 Action 配置设置为 AbandonAndSuspend 时，也会发生这种情况.

A difference I have noticed from the last question is that it can happen also when the configuration of the service Action on unhandled exception is set AbandonAndSuspend.

因此该方案是使用 AppFabric 持久性存储在 IIS 中托管的长期工作流服务.该服务执行一些操作，然后从数据库轮询结果.此轮询每 30 分钟进行一次.出于某种原因，WF 卡住了，什么也不做.检查 InstancesTable 我可以看到过去的待处理计时器和旧的 LastUpdateTime.

So the scenario is a long term Workflow service hosted in IIS using AppFabric persistence store. This service performs some actions and then polls the result from a database. This polling is done every 30 minutes. For some reason the WF gets stuck and doesn't do anything else. Checking the InstancesTable I can see a past pending timer and an old LastUpdateTime.

我发现的唯一解决方法是暂停然后恢复实例，这显然是一个痛苦的过程(在这种情况下大约有 5000 个实例).

The only workaround I found is to suspend and then resume the instances, which is obviously a painful process (there are around 5000 instances in this situation).

提前致谢

推荐答案

问题，如怀疑，与最大并发实例数有关.由于 WCF 中的某些技术问题可能不可用，因此有许多实例持续运行(重试对该 WCF 的调用)以应对最大并发实例数.因此，在每个检测周期激活的实例很少.感谢莫里斯的帮助

The problem, as suspected, was related to the maximum number of concurrent instances. Due to some technical problems in a WCF that might be unavailable, there were a number of instances continuously running (retrying a call to that WCF) that were coping that number of maximum concurrent instances. Due to that, there were very few instances activated on every detection period. Thanks Maurice for your help

这篇关于尽管没有书签和挂起计时器，AppFabric/WF 4.0 实例仍然卡住的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！