BizTalk FTP适配器有线行为当其中一个订户在发送端口组中无法访问时。 [英] BizTalk FTP Adapter Wired Behavior when one of subscriber is not reachable in send port group.

问题描述

嗨朋友们，

我想与过去三天的BizTalk 2006 R2 ftp适配器分享我的有线体验我一直在努力解决使用ftp适配器解决的所有已知问题，确实更改了许多设置但没有用。

场景和配置：

在我详细讨论这个问题之前，我想解释一下这个场景以及我想要实现的目标。其中一个客户端有一个场景，我们有一个ftp接收位置将文件发布到BizTalk 2006 R2和相同的三个ftp远程位置订阅。由于实时企业限制，我们无法在实时环境中测试相同的场景，并且在测试服务器上复制相同的场景，我们有四台服务器来满足场景需求。我们在局域网（LAN）连接的ftp服务器上设置了1个接收位置和3个发送位置。
它是基于接收端口的纯（CBR）内容路由，使用3发送将消息发送到3 ftp位置端口和发送端口组过滤器，相当没有编排和动态解决端点（DREP）模式的一些事情，简单来说，它不是一个复杂的集成，实际上非常简单。只是在没有任何开发工作的情况下使用了开箱即用的功能，并使用默认管道来通过。

问题区域：

一旦我们开始测试，我们在接收位置删除了几个文件（少于100个），并且消息传递完全正常，没有任何问题。之后我们遇到了一个测试场景，我的一个客户位置网络非常弱，并且由于远程位置的基础设施问题，它在一天内断了几次，复制问题并测试我们拔掉网络连接到LAN内的目标ftp服务器之一并丢弃了1000个文件，结果非常有线BizTalk 2006 R2向两个活动连接传递了600多条消息，其余所有消息都脱水并停止处理。最初我感觉它的性能问题，但BizTalk 2006 R2盒子我们安装在戴尔电源边缘2950与16 GB内存，当我查看系统监视器统计服务器甚至没有3％的处理器时间2 GB的内存消耗。

但是当我将未插入的服务器重新连接到网络几秒钟后，所有脱水的消息都正确地传送到目的地（每个活动的ftp位置上有400条消息，1000条插入不插电的弱位置）时，我真的很惊讶，繁忙的因素是我们的活动端口如何依赖断开的端口？根据pub子BizTalk基本架构，剩下的400条消息都没有任何依赖。我不确定，并且很难弄清楚它并说服客户是因为在真实情况下客户端网络连接在某些情况下不会出现几天。

什么原因是什么？你们中的任何一个人遇到过这种情况吗？

不知怎的，我怀疑网络问题！我想在所有服务器上执行netcap.exe诊断和很少其他网络，ftp服务器设置相关测试..也会做适配器记录...如果你认为任何诊断技术弄明白，请让我知道问题？

如果我这样做了，肯定会让你知道原因。我非常感谢您对上述任何帮助和看法。

谢谢，

Rajesh Gorla。

解决方案

尝试通过删除sendport组过滤器进行测试，如果您想将相同的消息发送到3个不同的位置，请将过滤器添加到3个发送端口和订阅。

Hi Friends,

 

  I would like to share my wired experience with BizTalk 2006 R2 ftp adapter, from last three days I have been working around and going thru all known issues addressed with the ftp adapter, did change many settings but no use.

Scenario and Configuration:

Before I go in detail about the issue i would like to explain the scenario and what i would like to achieve. One of client has a scenario where we have one ftp receive location to publish the files to BizTalk 2006 R2 and the same subscribed by three ftp remote locations. Since due to live enterprise constraints we could not able to test the same scenario on live environments and the same replicated on test servers where we have four servers to cater the scenario. We have a setup of 1 receive location and 3 send locations on local area network (LAN) connected ftp servers.
it is pure (CBR) content based routing based on receive port the messages are sent to 3 ftp locations using 3 send ports and send port group filter, fairly no orchestrations and dynamic resolution of endpoint (DREP) patterns some thing like involved, in simple words its not a complex integration at all in fact very simple . Just used out of box features with out any development efforts, and used default pipeline to pass thru.

Problem Area:

once we began testing we dropped few files(less then 100) in receive location and the message delivery worked absolutely fine without any issue .after all we have come across a test scenario where one of my clients location network is very weak and it breaks few times in a day due to the infrastructure issues at remote location, to replicate the issue and test the same we unplugged the network cable to one of destination ftp server within the LAN and dropped 1000 files, the results are very wired BizTalk 2006 R2 delivered more than 600 messages to two active connections and rest of all messages dehydrated and stopped processing. Initially i felt like its performance issue but BizTalk 2006 R2 box we have installed on dell power edge 2950 with 16 GB ram, when i looked in to the system monitor statistics server not even taking 3% processor time 2 GB of memory consumption.

But i was really surprised when i connected the unplugged server back on to network after few seconds all dehydrated messages are delivered to destination properly (400 messages on each active ftp locations and 1000 to unplugged weak location), the hectic factor is how come our active ports are dependent on the disconnected port? As per pub sub BizTalk basic architecture the rest of 400 messages delivered with out any dependency. am not sure and it is very hard to figure it out and convince the client be cause as per client in real scenario network connection do not turn up for couple of days on some occasions.

What is the cause? Any one of you guys come across this sort of situation?

Somehow i am suspecting the network issues!! i would like to carry out netcap.exe diagnosis and few other network, ftp  server setting related tests on all servers .. Also would be doing adapter logging ...please do let me know if you think any diagnosis techniques to figure it out the issue?

If I get this working,,, surely will let you know the cause. I really appreciate any help and your views on above.

Thanks,

Rajesh Gorla. 

解决方案

try to test by removing sendport group filter, if u want to send the same message to 3 different locations, add filters to 3 send ports and subscribe.

这篇关于BizTalk FTP适配器有线行为当其中一个订户在发送端口组中无法访问时。的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！