BizTalk低延迟-调用C#到WCF-Published Orchestration的响应时间问题 [英] BizTalk low latency - response time issue calling C# to WCF-Published-Orchestration

问题描述

从C#程序调用WCF发布的业务流程通常需要不到一秒的响应时间.但是，在某些情况下，在C#程序中的调用与业务流程中的第一条跟踪消息之间可能要花费20-50秒.运行WCF的C#在HIS/HIP(主机集成服务/CICS主机启动的处理)下运行.

Calling a WCF published orchestration from a C# program usually is sub-second response time. However, on some occasions, it can take 20-50- seconds between the call in the C# program and the first trace message from the orchestration. The C# that runs calls the WCF runs under HIS/HIP (Host Integration Services/CICS Host-Initiated Processing).

几乎每次我重新启动HIS/HIP服务时，我们的响应时间都很慢，因此CICS超时.我还担心如果事情变冷"，白天可能会发生这种情况-换句话说，可能是事物被缓存了.即使是JIT初次编译也不应该花20-50秒吗?似乎很奇怪的另一件事是，响应时间很慢似乎是业务流程的负载，该业务流程是在BizTalk服务下运行的，而不是我循环的HIP/Service.

Almost everytime I restart the HIS/HIP service, we have a very slow response time, and thus a timeout in CICS. I'm also afraid it might happen during the day if things "go cold" - in other words maybe things are being cached. Even JIT first-times compiles shouldn't take 20-50 seconds should they? The other thing that seem strange is that the slow response time seems to be the load of the orchestration, which is running under the BizTalk service, not the HIP/Service which I cycled.

担心的是，当我们上线时，早上的第一个用户(或在冷拼"之后将获得超时).他们第二次尝试超时后，它总是很快.

The fear is that when we go live, the first user in the morning (or after a "cold-spell" will get the timeout). The second time they try it after the time-out, it is always fast.

我通过重新启动以下各项进行了一些测试: 1)BizTalk服务 2)IIS 3)HIS/HIP交易集成商(HIP服务)

I've done a few tests by restarting each of the following: 1) BizTalk services 2) IIS 3) HIS/HIP Transaction Integrator (HIP Service)

重新启动其中任何一个都可能导致大约20秒的延迟. 重新启动所有3个命令就像是死亡之吻-在编排过程中出现第一条痕迹之前，大约延迟了60秒.

Restarting any one of them tends to cause about a 20 second delay. Restarting all 3 is like the kiss of death - about a 60 second delay before first trace appears from orchestration.

即使重新启动HIP服务，HIP程序也总是快速给出其第一条迹线.不知道为什么重新启动HIP会减慢业务流程的启动.

The HIP program always gives its first trace quickly, even when the HIP service is restarted. Not sure why restarting HIP slows down the starting of the orchestration.

谢谢

尼尔·沃尔特斯

推荐答案

我也看到了MQSeries适配器的这种行为.一段时间不活动后，由于与不活动状态而导致与MQSeries进行通信的COM +组件将关闭.

I have seen this kind of behavior with the MQSeries adapter as well. After a period of inactivity the COM+ components which enable communication with MQSeries will shut down due to inactivity.

我们有一个10分钟的计时器，它将强制发出某种保持活动的消息.我不知道您是否可以发送无损呼叫，或者是否可以为此目的在系统中建立一个.

What we had was a 10 minute timer which would force some sort of a keep-alive message. I don't know if you have a non-destructive call which can be sent, or if you can build one into the system just for this purpose.

这篇关于BizTalk低延迟-调用C#到WCF-Published Orchestration的响应时间问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！