- This topic has 1 reply, 1 voice, and was last updated 9 years, 3 months ago by
.
-
Posts
-
-
Hi,
I am building a business process in biztalk. There are mutiple orchestration which are executed during the processing of a message. Sometimes, any of it may encountere an error and the service instance is suspended. Now, if i have to redeploy the orchestration due to some error fix,
Is there any way to resume the the very same suspended instance , If yes the how? (Biztalk do not allow to deploy if there are any service instances alive)
If not then what should be done in this case. One option is to save the message, terminate the instance, redeploy and execute again. Is ther any other way?
Thanks in advance for any help or suggestions.
-
Once an orchestration has suspended, it can only be resumed with exactly the same code that it started with.
There is a cheat, but this can be risky and can cause worse problems. It should only be used in absolute emergencies and make sure you save all your messages first. You can rebuild your assembly, stop the host instance that uses it, remove the original assembly from the GAC, add the new assembly to the GAC and restart the host instance. This should only be tried if you are changing a schema or a map. Changes to orchestration code will typically crash and burn.
You best option is to design your orchestrations so they do not fail/suspend. Make use of the Scope shape with exception handlers to take corrective action. Check out the ESB Guidance (called ESB Toolkit on Biztalk 2009). It has a number of Exception handling components that help in building robust orchestrations.
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.