|
Home > Archive > BizTalk Server General > September 2004 > Service will not dehydrate
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 |
Service will not dehydrate
|
|
|
| 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
| |
| Cristian Salvan [MSFT] 2004-09-23, 5:51 pm |
| I don't think this is a bug. Orchestration instances are dehydrated only
when there are not enough resources to keep them in memory. You should not
care about the service instance's state, unless it eats up a lot of your
memory.
Is this the case? Are you hitting any issues?
Thanks,
Cristi
> X-Tomcat-NG: microsoft.public.biztalk.general
>
> 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
>
|
|
|
|
|