消息的一部分在Construct的末尾包含一个空值 [英] The part of message contained a null value at the end of Construct
问题描述
亲爱的所有人，
我们面临以下错误，从今天早上开始，如果我们运行编排10次，则抛出此错误9次并且1次工作正常。
消息'MsgRq'的部分'part'在构造块的末尾包含空值
在我们调试orch时，错误正在讨论的消息是业务流程收到的消息。正确地收到整个消息，然后它通过构造消息形状，其中它在地图中使用，之后有一个发送形状，当我在此阶段检查消息部分值时（即在通过之后）构造形状）它是完美的找到，有效的大小和数据，但在执行发送形状后，它变为空，大小-1，没有明显的原因，发送形状正在写一个文件到Unix，这是一个不同的消息写在那里。我们需要在下一步收到消息，这是发送到TCP端口，而我们遇到上述错误。正如你所看到的那样，它提到消息在Construct块的末尾是Nulled，但正如我所写的那样，在它通过一个Construct形状之后就很好了。或者我们也在使用BizTalk server 2006，对于类似类型的消息，biztalk 2004有一个修补程序，但是它讨论了嵌套的业务流程和调用orch。形状，我们在我们的orch中没有做这些。
在这方面请帮助我们。
问候
Sajid
Dear All,
We are facing the following error, from this morning, say if we run the orchestration 10 times, 9 times this error is thrown and 1 times it works fine approx.
The part 'part' of message 'MsgRq' contained a null value at the end of the construct block
The message the error is talking about is the one recieved by the orchestration, when we debug the orch. it is recieved correctly, the whole message, then it goes through a construct message shape in which it is used in a map, after that there is a send shape, when I check the the message part value at this stage (i.e. after passing the construct shape) it is perfectly find, with valid size and data, but after that Send shape is executed, it becomes null, and size -1, to no apparent reason, that send shape is writing a file to Unix and thats a different message written there. We need the received message at the next step, which is a send to a TCP port, rather we are greeted with above mentioned error. As you see it mentions that message is Nulled at the end of Construct block, but as I wrote, its fine after it passes the one Construct shape there is in the orch.
Also we are using BizTalk server 2006, there is a hotfix for biztalk 2004 for a similar type of message, but that talks about nested orchestrations, and call orch. shapes, we are doing none of these in our orch.
Kindly help us in this regard.
Regards
Sajid
推荐答案
它是十分之一的传入消息，或者是您测试的不同消息吗？这对我来说听起来像是地图就是问题所在。你有使用VS和映射工具测试功能失败的测试消息？那么测试其中一条失败的消息当然是非常有趣的...
Is it the same incoming message that works one out of ten times or is it different messages you test with? It sound to me like it could be the map thats the problem. Have you tested messages that fails using VS and the mapping tools testing capabilities? Then it'd of course be very interesting to test one of the messages that fails ...
此外，您是否使用例如DebugView（这里的示例）。我发现通过HAT使用调试选项更加容易和快捷。
Also, do you have tracing in you orchestration using for example DebugView (example here). I find it much easier and faster to use then the debugging options via the HAT.
让我们发布。
Richard Hallgren
Richard Hallgren
http://www.richardhallgren.com
这篇关于消息的一部分在Construct的末尾包含一个空值的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
