在自定义管道中进行Debatching和添加名称空间会因大邮件而失败 [英] Debatching and add namepaces in custom pipeline fails with large messages

问题描述

大家好，

我已经构建了一个自定义管道组件，可以动态地将命名空间添加到消息中。传入的消息在xml反汇编程序中被分配，然后根据xpath在每个xml中设置名称空间。由于体系结构
，我无法使用业务流程来处理消息。

I have build an custom pipeline component that add namespaces dynamically to messages. The incoming message is debatched in the xml disassembler and afterwards the namespaces are set in each xml according to an xpath. Due to the architecture I can't use an orchestration to process the messages.

小批量生产一切正常，但批量较大则不稳定。大多数已下载的邮件都没有到达自定义渠道。 邮件失败，错误"对象引用未设置为对象。"

With small batches everything works fine, but with larger batches it isn't stable. The most of the debatched messages doesn't arrive in the custom pipeline. The message fails with the error 'Object reference not set to an object.'

有谁知道回答解决这个问题？

Does anyone knows the answer to solve this problem?

亲切的问候，

Lenny

推荐答案

你好Lenny，

Hi Lenny ,

你能尝试调试你的管道自定义组件以隔离对象引用的原因"未设置为对象错误的实例" 。

Can you try debugging your Pipeline custom component to isolate the reason for object reference" not set to instance of object error " .

您也可以尝试使用不同的Pipeline组件。使用xml dissembler以及在管道的不同阶段添加命名空间组件，并尝试调试任何异常（如果引发）。

You can also try to have different Pipeline component for both purpose . Use xml dissembler along with add namespace component at different stages of pipeline and try to debug for any exception if raised .

注意：可能存在您的批量消息不一致的情况。

Note : There may be case that your bulk message is not consistent .

谢谢

Abhishek

这篇关于在自定义管道中进行Debatching和添加名称空间会因大邮件而失败的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！