Ordered Delivery for Orchestrations
8/30/2012 2:39:04 PM
User(s) can reproduce this bug
BizTalk Server version Next, Ordered Delivery and Zombies
It might be possible the BizTalk Server version Next will implement the automatic Ordered Delivery for Orchestrations, with pattern similar to the Ordered Delivery in Send Ports.
Three new Orchestration parameters are shown up there [please, see the file]: Ordered Delivery, Stop on Exception, and Recycle Interval (in seconds). Maybe the "Recycle After [N] messages are received [sent]" would be helpful for one more scenario.
Ordered Delivery parameter works in the same way as the Ordered Delivery parameter of the Send Port. Now we don’t have to build the Convoy Orchestration manually. No more Loop inside Orchestration.
If the Ordered Delivery parameter set up to True, the Orchestration is working as a Singleton. The first Receive shape receives all correlated messages in sequence. Correlation set is created implicitly regards of the Activation Subscription expression.
There might be several limitations for this kind of Orchestration. The most important is: only one Receive shape is permitted here.
There are two big advantages of this new feature:
1.Simplified Orchestration design for the Ordered Delivery.
2. No more Zombies. The Orchestration instance is recycled in controllable way, when no messages, matched the Orchestration Subscription, are placed in the MessageBox.
This feature would mitigate a great disadvantage of the BizTalk, inability to create a robust Ordered delivery scenarios.
BizTalk 2010 Beta
it is a suggestion
to post a comment.
Please enter a comment.
to post a workaround.
Please enter a workaround.
© 2013 Microsoft