I have two orchestrations that sometimes dehydrates and
sometimes they dont. They should dehydrate while waiting
for a correlating response, but after I push through a lot
of messages they remains active.

I can see that they are waiting for a incoming message,
and should be dehydrated, but they shows up as active.

If I restart the host underwhich the orchestrations runs,
the stuff starts working properly again and dehydrates.

This was a bug which was addressed in the rollup package,
which is installed. But I still have this problem.

Any suggestions?

-Gary

[ Post a follow-up to this message ]

Hi,

i have the same problem... I send a message and wait for answer but
sometimes the orchestration does not dehydrate. I tried to include a dummy
expression shape between send and receive. It seems to be the problem occure
s
not as often as before - but it solves not the problem! I assume it has
something to do with Scopes and/or transactions because my send shape reside
s
inside a scope while the following receive shape does not...

Dirk

"Gary" wrote:

> I have two orchestrations that sometimes dehydrates and
> sometimes they dont. They should dehydrate while waiting
> for a correlating response, but after I push through a lot
> of messages they remains active.
>
> I can see that they are waiting for a incoming message,
> and should be dehydrated, but they shows up as active.
>
> If I restart the host underwhich the orchestrations runs,
> the stuff starts working properly again and dehydrates.
>
> This was a bug which was addressed in the rollup package,
> which is installed. But I still have this problem.
>
> Any suggestions?
>
> -Gary
>

[ Post a follow-up to this message ]

Hi,

The orchestration engine will decide when it needs to dehydrete an
orchestration instance. It does this by calculating when it thinks the
orchestration will become active, and also how much memory it has available.
As dehydration is resource intensive, it will not do this if it does not nee
d
to. Restarting the host will force all the active orchestrations to be
dehydrated (correct?). Also, when memory becomes scarse, this will happen
more often.

I have noticed BizTalk seems to take care of dehydration pretty well, but
you can't determine when, or if, it will happen. If you want to get a better
insight into this process, bang up PerfMon, and add the Dehydration related
counters in the XLANG/s Orchestrations setion. (The dehyration threshold is
used to determine if an instance will be dehydrated.)

Cheers,

Alan


"Dirk" wrote:
[vbcol=seagreen]
> Hi,
>
> i have the same problem... I send a message and wait for answer but
> sometimes the orchestration does not dehydrate. I tried to include a dummy
> expression shape between send and receive. It seems to be the problem occu
res
> not as often as before - but it solves not the problem! I assume it has
> something to do with Scopes and/or transactions because my send shape resi
des
> inside a scope while the following receive shape does not...
>
> Dirk
>
> "Gary" wrote:
> 

[ Post a follow-up to this message ]

Strange - I think I'm having the opposite problem.   I'm calling a web
service, and it dehydrates on the Send, then it never rehydrates after the
web service supposedly is finished, i.e. it stays dehydrated for hours, and
web service trace/log shows that it did a return.   Any ideas here?

Neal Walters
http://Biztalk-Training.com

[ Post a follow-up to this message ]