- This topic has 1 reply, 1 voice, and was last updated 9 years, 2 months ago by
.
-
Posts
-
-
Hi Experts:-
While making a call to Siebel Webservice from a Biztalk Orchestration, we are running out of Threads using the .NET ThreadPool. It looks like the orchestration thread that makes a call to the webservice is also in the threadpool and as we are instantiating more orchestration threads they occupy the pool and then keep waiting for a thread to become available. This generates the deadlock situation. We tried changing the high/low watermarks to a low number and that solves this problem but makes the overall performance really low. I am trying to search a solution and hitting things like setting some registry settings under HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services
for Min/Max Worker Threads.Somebody having first hand experience with this/similar problem….mind giving an advice? Is there a way to restrict number of threads an orchestration can instantiate at a time?
Thanks!
-
Scion,
If you have both the adapter and the orchestrations bound to the same application host, then they basically share the same threadpool, which might cause problems. If you have need for quite a few threads, it is usually better to set up things so that the adapter (in your case the Siebel adapter send handler) and the orchestrations are bound to different application hosts.
For example, you might just create a second Application Host and make sure your orchestrations run there and leave the default app host just for the adapters. With this, both will run in separate processes which should make things a little easier.
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.