RE: Rehydration on server Restart.

Hi Sundeep,

You won't be able to directly change the schedule of the dehydrated
instances to delay each of them by a particular time interval. However, if
the design of your system allows it, you could consider using a controller
or dispatcher framework which would involve a singleton orchestration which
is responsible for starting off multiple child orchestrations. I believe
there are custom BizTalk solutions which are currently using this approach.
I'll also follow up with several people internally regarding the scenario
you've outlined.

Regards,
Sumitra Sujanani [MSFT]

--------------------
From: sundeeps@xxxxxxxxx
Newsgroups: microsoft.public.biztalk.general
Subject: Rehydration on server Restart.
Date: 8 May 2006 00:26:22 -0700
Organization: http://groups.google.com
Lines: 16
Message-ID: <1147073182.398943.318810@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
NNTP-Posting-Host: 202.144.61.68
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1147073187 25583 127.0.0.1 (8 May 2006
07:26:27 GMT)
X-Complaints-To: groups-abuse@xxxxxxxxxx
NNTP-Posting-Date: Mon, 8 May 2006 07:26:27 +0000 (UTC)
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1;
NET CLR 1.1.4322; InfoPath.1),gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@xxxxxxxxxx
Injection-Info: e56g2000cwe.googlegroups.com; posting-host=202.144.61.68;
posting-account=Qsq-qA0AAAB1wbX7khteStUIJxOh7RvZ
Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS01.phx.gbl!newsfeed00
sul.t-online.de!t-online.de!border2.nntp.dca.giganews.com!border1.nntp.dca.
giganews.com!nntp.giganews.com!postnews.google.com!e56g2000cwe.googlegroups.
com!not-for-mail
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.biztalk.general:37282
X-Tomcat-NG: microsoft.public.biztalk.general

Hi,

We are using BizTalk 2004 in our environment with .Net Framework 1.1.
We are facing one issue with the long dhydrated orchestrations. Problem
occurs when the server reboots after maintenance period of few hours.
In this case, all the orchestration instances that were scheduled to be
run during the time when the server was down or maintenance wakes up
and BTS fires them simultaneously. Some services that are called in the
orch are not able to handle these many requests simultaneously.

I was wondering if we have a way by which we can change the schedule of
the dehydrated instances and delay each of them by say original time +
2-3 hrs ?

Thanks in advance..



This posting is provided "AS IS" with no warranties, and confers no rights.

Connected Systems Division Team


Get Connected!
Meet and interact with key BizTalk Server program managers, developers, and
testers, and let them and other BizTalk Server community team members and
Most Valuable Professionals help you solve your product questions.

Navigate to http://msdn.microsoft.com/subscriptions/support/ in your
webrowser and register as a managed customer to receive MSDN Managed
Newsgroup Support!

MSDN managed newsgroups are available in English to MSDN Universal,
Enterprise, Professional, and Operating Systems subscribers to receive
free, unlimited technical support on select Microsoft technologies as well
as to share ideas with other subscribers.

.

Relevant Pages