|
Home > Archive > BizTalk Server Orchestration > July 2005 > Update long running transaction in production system
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Update long running transaction in production system
|
|
| Eddie Tse 2005-07-12, 7:55 am |
| Hi All,
Just want to get some insight on how people are updating their long running
orchestration in production system. Say I've got an orchestration that can
take 2 weeks to run, if I need that change it because of a process change,
what happens to all those in flight orchestration? I need to kill all
running instance to deploy the new orchestration assembly.
So the simple way thing to do is avoid long running transaction or break
them out into smaller orchestrations. Just want to know how do you tackle
your production orchestration update?
Regards,
Eddie
| |
| WenJun Zhang[msft] 2005-07-13, 7:54 am |
| Hi Eddie,
This is a pain for all kind of application development involving
long-running transactions(LRTs). If it's still in software
testing/debugging stage, terminating running processes to make
changes is acceptable. However for a production environment, you
should prevent changing the code anymore. For new released version
must be deployed, check HAT first to make sure there is no active or
pending instances in dehydrated state before shutdown everything.
Thanks.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
|
|
|
|
|