| Saravana Kumar 2005-04-17, 7:54 am |
| Hello Dirk,
I was reading this article from the Biztalk server performance guys, there
is a solution to control the thread pool....I've just removed the porting
required for you
By default the messaging engine creates 10 threads/cpu for
publishing messages.
To specify the messaging thread pool size
1. Click Start, and then click Run.
2. In the Run dialog box, in the Open box, type regedit, and then click OK.
3. In Registry Editor, expand HKEY_LOCAL_MACHINE, expand SYSTEM, expand
CurrentControlSet, expand Services, right-click BTSSvc* (you would first
need to determine which of the BTSSvc* regkeys correspond to the host
corresponding to the receive handler), point to New, click DWORD Value, type
MessagingThreadPoolSize, and then press ENTER.
4. In Registry Editor, double-click MessagingThreadPoolSize.
In the Edit DWORD Value dialog box, in the Value data box, type a number
between 1 and 30, and then click OK.
5. Note for Custom Adapters:
If you have verified all of the above conditions and if you think your
custom receive/send adapter is causing the OOM conditions, then you need to
look at the source code of your adapter and verify the following:
for the full article visit
http://blogs.msdn.com/biztalkperformance/default.aspx
--
Cheers
Saravana [MCP - Biztalk Server 2004]
http://www.digitaldeposit.net/blog
"Dirk" <Dirk@discussions.microsoft.com> wrote in message
news:35554668-83D6-4292-87BE-ED86239A478F@microsoft.com...
> Hi,
>
> is there a way to limit the number of concurrent threads/messages per host
> or per orchestration? I have a problem with the Threadpool (while calling
> a
> number of WebServices parrallel) and want to restrict the number of
> orchestration instances running parrallel.
>
> Cheers
>
> Dirk
>
|