Comments on: Yet Another Non-Deterministic BizTalk Zombie Pattern http://www.modhul.com/2008/06/08/yet-another-non-deterministic-biztalk-zombie-pattern/ Experiences of a UK BizTalk Consultant Mon, 15 Mar 2010 01:21:26 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Gregory Van de Wiele http://www.modhul.com/2008/06/08/yet-another-non-deterministic-biztalk-zombie-pattern/comment-page-1/#comment-128 Gregory Van de Wiele Mon, 09 Jun 2008 12:22:00 +0000 http://www.modhul.com/?p=143#comment-128 Joe Duffy, whois an expert on all things multi-t and locking, and regularly writes for MSDN magazine wrote this once: 13. A race condition or deadlock in library code is always a bug. http://www.bluebytesoftware.com/blog/PermaLink,guid,f8404ab3-e3e6-4933-a5bc-b69348deedba.aspx BizTalk is the library in this case and this problem should have been better addressed by MS. A workaround for certain scenarios much like the one of Victor: disable the receive location by code in the orchestration, wait twice the cache interval (forgot why exactly) and asynchronously start orchestration that enables the RL. Antoher workaround that I used for singleton: a service window around midnight for the RL, inside the delay branch of the listen shape you can check the time and if you are inside the service window (take a margin here + or - 1 or 2 minutes) you can more or less safely recycle. That solved the problem for me. I guess it is not bullet proof either but it worked for us. Gregory Joe Duffy, whois an expert on all things multi-t and locking, and regularly writes for MSDN magazine wrote this once:

13. A race condition or deadlock in library code is always a bug.

http://www.bluebytesoftware.com/blog/PermaLink,guid,f8404ab3-e3e6-4933-a5bc-b69348deedba.aspx

BizTalk is the library in this case and this problem should have been better addressed by MS.

A workaround for certain scenarios much like the one of Victor: disable the receive location by code in the orchestration, wait twice the cache interval (forgot why exactly) and asynchronously start orchestration that enables the RL.

Antoher workaround that I used for singleton: a service window around midnight for the RL, inside the delay branch of the listen shape you can check the time and if you are inside the service window (take a margin here + or – 1 or 2 minutes) you can more or less safely recycle. That solved the problem for me. I guess it is not bullet proof either but it worked for us.

Gregory

]]>