I have an orchestration that uses correlation and can wait on the receive port for up to 8 hours before getting the correlation response
My problem is that the orchestrations do not always dehydrate and eventually I have dosens of open orchestrations in Active state and my Biztalk get stuck.
Unfortunately BT (orchestration engine in particular) does not give us absolute control over this process. This can not be done programmatically, it’s under contol of orchestration engine. You can configure certain aspects in Biztalk’s configuration file (defalut config file doesn’t even list these values but it uses default values) but this is probably not what you’d ultimately want. For example, [by default], an orchestration will wait for 1800 sec at receive location before dehydrating. For send ports it may keep history of how long it used to wait and based on that value dehydrate.
Author
Posts
Viewing 1 reply thread
The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.