When I start my orchestration after a period of downtime, the system
plays "catch up" with the accumulated messages (the receive adapter
ran during downtime) and spawns an unknown number of orchestrations.
This causes difficulty with the client system due to a limited number
of available connections.

Is there a recommended/documented/both way to restrict the number of
orchestrations running concurrently to keep from overwhelming the
client system?  Any help appreciated.

Ed

[ Post a follow-up to this message ]

No,  this is currently not supported by BizTalk Server 2004.  There exists a
paper that describes a "resource dispenser" pattern.  However, unless you
REALLY need this, I would *not* advise you to use this in production.  In
most scenario's this will likely turn out to be unmanageble.  Note: this is
*my* personal opinion, which does *not* reflect the Microsoft's thinking on
this.  Anyway, I'd advise you to request for a fix.

Best regards,
Christof

"Ed Mathias" <edward_mathias@hotmail.com> wrote in message
news:bceae306.0407191241.634ea5c8@posting.google.com...
> When I start my orchestration after a period of downtime, the system
> plays "catch up" with the accumulated messages (the receive adapter
> ran during downtime) and spawns an unknown number of orchestrations.
> This causes difficulty with the client system due to a limited number
> of available connections.
>
> Is there a recommended/documented/both way to restrict the number of
> orchestrations running concurrently to keep from overwhelming the
> client system?  Any help appreciated.
>
> Ed

[ Post a follow-up to this message ]

Please refer to the BizTalk 2004 Performance Whitepaper which
can be downloaded from the following link:
http://www.gotdotnet.com/team/wsser...Performance.zip

This explains how to set the High/Low Memorymark parameters.
Please use the downlaodable tool to change these values.

Thanks,
MRoze

This posting is provided "AS IS" with no warranties, and confers no rights.
EBusiness Server Team
[vbcol=seagreen] 
exists a[vbcol=seagreen] 
is[vbcol=seagreen] 
on[vbcol=seagreen] 

[ Post a follow-up to this message ]

Michael,

please correct me if I'm wrong!

Those high/low memorymark parameters affect the whole server, not just the
orchestration type or the host it runs in.

Best regards,
Christof

--
Christof [Microsoft BizTalk Server MVP]

"Michael Roze [MSFTF]" <mroze@online.microsoft.com> wrote in message
news:fz7W08LdEHA.3204@cpmsftngxa10.phx.gbl...
> Please refer to the BizTalk 2004 Performance Whitepaper which
> can be downloaded from the following link:
> http://www.gotdotnet.com/team/wsser...Performance.zip
>
> This explains how to set the High/Low Memorymark parameters.
> Please use the downlaodable tool to change these values.
>
> Thanks,
> MRoze
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> EBusiness Server Team
> 
> exists a 
you[vbcol=seagreen] 
In[vbcol=seagreen] 
> is 
> on 
>

[ Post a follow-up to this message ]

That is correct.

Thanks,
MRoze

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

--------------------[vbcol=seagreen] 
<Ol76acncEHA.3300@TK2MSFTNGP09.phx.gbl>
<fz7W08LdEHA.3204@cpmsftngxa10.phx.gbl>[vbcol=seagreen] 
this[vbcol=seagreen] 
thinking[vbcol=seagreen] 
number[vbcol=seagreen] 

[ Post a follow-up to this message ]