|
Home > Archive > BizTalk Server Orchestration > February 2004 > Why are XLang Instances kept running ?
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 |
Why are XLang Instances kept running ?
|
|
|
| I'm using a very simple XLang schedule which (by means of
COM) extracts some data from an XML and sends this via a
WinSock channel to another machine synchronously. When
the reply from this machine is OK, data is entered into a
database and the schedule is left. This runs in a
transaction.
It works fine when messages are posted to BizTalk in a
once-in-a-while manner, but now, I'm putting a heavy load
onto BizTalk via a FileReceiver (could be up to 10 or more
messages dropped at the FileReceiver per seconds).
After a small while, when XLang Monitor shows that there
are 5 or more instances running, it may happen that the
oldest messages are not threaded anymore.
Does anyone have a clue how to overcome this ?
Thanks. John.
| |
| Sameer.Surve@ilg.com 2004-02-08, 8:42 am |
| I think the problem you are trying to solve is how to "throttle" the
orchestration instances so that they do not overwhelm the processing
system.
If this is the issue, then you might want to attach the orchestration
to a XLANG schedule pool which can be controlled (via instantiation
counters). Do not forget to appropriately set the wait time too.
XLANG schedule pool is available within COM+ services.
To attach the particular orchestration to XLANG schedule pool, open
the BEGIN icon and attach the orchestration to the particular pool you
want.
Hope this helps.
"John" <anonymous@discussions.microsoft.com> wrote in message news:<061d01c3dab2$b2dba9c0$a001280a@phx.gbl>...
> I'm using a very simple XLang schedule which (by means of
> COM) extracts some data from an XML and sends this via a
> WinSock channel to another machine synchronously. When
> the reply from this machine is OK, data is entered into a
> database and the schedule is left. This runs in a
> transaction.
>
> It works fine when messages are posted to BizTalk in a
> once-in-a-while manner, but now, I'm putting a heavy load
> onto BizTalk via a FileReceiver (could be up to 10 or more
> messages dropped at the FileReceiver per seconds).
>
> After a small while, when XLang Monitor shows that there
> are 5 or more instances running, it may happen that the
> oldest messages are not threaded anymore.
>
> Does anyone have a clue how to overcome this ?
>
> Thanks. John.
|
|
|
|
|