BizTalk渗透的消息未被提取 [英] BizTalk debudrated messages not picked up

查看:63
本文介绍了BizTalk渗透的消息未被提取的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

  我们有一个带有异常块的orchesrtaion来捕获它内部的所有异常。此业务流程正在调用WCF服务并返回响应消息。 我们有1分钟的超时财产。我们在负载平衡环境中处理近10,000个
消息。我们有4个前端服务器,DB是ACTIVE / ACTIVE集群。我们注意到一些QF进入脱水模式并且从未再次发现。在任何时候,我们通常会在脱水模式下看到1到10条消息
,我们肯定没有达到节流阶段。每当我们重新启动主机实例时,这些消息都会从脱水阶段中获取并正确处理。由于这个问题,我们几乎每天都需要重启我们的主机实例
。任何人都可以让我知道我们需要做些什么来解决这个问题。我们正在使用BizTalk Server 2009企业版。在此先感谢。

   We have a orchesrtaion with with exception block to capture all the exceptions inside it. This orchestration is calling a WCF service and return a response message.  We do have a time out property of 1 minutes. We process almost 10,000 messages in our load balancing environment. We have 4 front end servers and DB is ACTIVE/ACTIVE clustered. We have noticed that some of the QFs goes into dehydrated mode and it never picked up again. At any point of time we usually see 1 to 10 messages in the dehydrated mode and we are certainly not reaching throttling stage. Whenever we restart the host instances, these messages are picked up from the dehydrated stage and getting processed properly. Due to this issue, we need to restart our host instances almost everyday. Can anyone please let me know what we need to do to fix this issue. We are using BizTalk Server 2009 enterprise edition. Thanks in advance.

推荐答案

消息在什么阶段脱水?可能是因为发送端口上配置的重试周期和间隔?您的发送/接收是否已退出作用域的Web服务部分?

At what stage are the messages getting dehydrated? Could it be because of the retry period and interval configured on the send port? Are your Send/Receive regading the web service part of a scope?

问候。


这篇关于BizTalk渗透的消息未被提取的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆