BizTalk 2013R2:为什么业务流程根据业务流程调试器终止后会初始化? [英] BizTalk 2013R2: Why does my orchestration initialise after being terminated according to the Orchestration Debugger?

问题描述

我目前正在诊断BizTalk环境中一些重复出现的问题，并且当前就是僵尸消息的问题.我知道造成这些错误的条件，并且在诊断业务流程并使用业务流程调试器时，我看到当消息达到终止形状时，便会进行初始化.

I am currently looking at diagnosing some reoccurring issues within a BizTalk environment and currently that is the issue of zombie messages. I am aware of the conditions that create these errors and whilst diagnosing the orchestration and making use of the Orchestration Debugger, I see that when a message has hit a terminate shape, it is followed by an initialisation.

业务流程的一般结构如下:

The general structure of the orchestration is as follows:

第一个作用域是一个长时间运行的事务，在该作用域之后的循环中，有一个监听形状，等待消息等待10秒钟.如果消息及时到来，它将进入另一个长期运行的事务.在某种程度上就像一个单身汉?这两个示波器共享相同的逻辑接收端口并相互关联，只有一个奇怪的部分是如何在侦听形状内部的循环内重复第一个示波器. (编排是我自己编写的应用程序庞然大物的一部分.)

The first scope is a long-running transaction and within the loop after that scope, there is a listen shape that waits for a message for 10 seconds. If a message comes in time, it enters another long-running transaction. It's like a singleton in a way? Both scopes share the same logical receive port and are correlated, only odd part is how the first scope is repeated within the loop that's inside the listen shape. (Orchestration is part of a behemoth of an application that wasn't written by myself.)

终止之后(实际上是什么导致这种情况发生的)初始化会引起僵尸，如果是的话，业务流程的结构和事务是否是造成僵尸的原因?还是我看错地方了?.

Would this initialisation after a termination (what actually causes this to happen?) cause zombies, if so is the structure of the orchestration and the transactions a cause of this? Or am I looking in the wrong place?.

让我知道是否有任何其他信息可以帮助您！

Let me know if there's any extra information that can help!

推荐答案

在Orchestration调试器中，它将显示开始的时间以及结束时的图标略有不同.因此，您所看到的是业务流程的结束.

In the Orchestration debugger it will show when something start and also when it ends with slightly different icons. So what you are seeing is the end of the Orchestration.

不，不会造成僵尸.僵尸发生在它结束了侦听某些内容的逻辑接收位置(并且正在拆除实例订阅)并且在编排完全结束之前到达了与该订阅匹配的另一条消息之后.

No, that will not cause zombies. Zombies occur after it ends the logical receive location that listens for something (and it is tearing down the instance subscription) and another message arrives that matched that subscription before the Orchestration has fully ended.

这篇关于BizTalk 2013R2:为什么业务流程根据业务流程调试器终止后会初始化?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！