Re: Thread shortage - performance recommendations please

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Greg Forsythe (greg.forsythe_at_unisys.com)
Date: 01/07/05 

Date: Fri, 7 Jan 2005 19:23:44 +1300

I think you might find the thread-pool error is being returned by the
receiver of the message - i.e. the IIS server hosting the web service. Check
out KB#821268.

There is a Biztalk Performance white paper that specifies performance
characteristics such as high an low water marks

You may need modify the Machine.config on the receiving end and the
BiztalkMgmtDb (high an low water marks) to balance this interface.

I had a similar situation 2 CPU Biztalk server -> 4 CPU IIS Server
Biztalk default high water mark is 100 -> 200 concurrent sends
IIS -> 25*4 = 100 threads

I lowered the Biztalk high water mark to 50 and the free thread error
message almost disappeared

Greg

"kartikp@online.microsoft.com" <anonymous@discussions.microsoft.com> wrote
in message news:00a101c4f428$990223e0$a501280a@phx.gbl...
>
> Is there any reason you are not using the inbuild Biztalk
> SOAP send adapter.
>
> Here are some tips.
>
> 1) The first thing you need to do is to make sure that you
> have a separate host for your Soap send adapter.
> If you keep it in the default host
> (BiztalkApplicationHost) then orchestrations will be
> competing with SOAP send adapter for the same threadpool.
>
> By isolating SOAP send adapter into its own process, you
> will be able to get more threads.
>
> 2) If you determine that your soap send adapter still
> chokes after hitting some number of concurrent requests,
> then you should have a configurable value for the number
> of concurrent/inflight messages that will be processed by
> your adapter.
>
> i.e. if your adapter is already processing 20 (for e.g)
> concurrent requests, and if the Biztalk messaging engine,
> gives you a new message, then your adapter should block
> the engine thread, till your inflight/concurrent requests
> are below 20.
>
> This will make sure that you don't overdrive the .net
> thread pool.
>
>
> >-----Original Message-----
> >Hi guys,
> >Have written a send adapter (using wizard) that makes
> some SOAP calls, each
> >call takes round a second to complete.
> >When passing a moderate amount of messages (400) through,
> processor/disk
> >usage is initially high, but drops off after a short
> time, when the event log
> >gets many warnings that there are not enough free threads
> in the threadpool.
> >After a few mins, the warnings become errors. HAT shows
> many messages
> >remaining - some "Active", some "Completed with discarded
> messages", some
> >"Suspended (resumable)". Message processing appears to
> halt altogether, and
> >nothing's going on in perfmon. Telling messages in HAT to
> resume gives error
> >that he can't - "maybe a service instance is already
> closed, or there is a
> >control message" (translated, may not be exact).
> >
> >The adapter has a batch size of 100, have reasonable
> memory (1GB), processor
> >and bandwidth.
> >How would you guys recommend I try to tune the server?
> (excluding "look in
> >the performance doc", which I didn't find too useful)
> >Some I thought of are
> >1. writing a server to spool outgoing messages, and
> >2. writing my own threadpool class for the adapter, with
> more than 25 (I
> >think is the limit?) threads available
> >
> >It's frustrating because I believe Biztalk can apparently
> handle loads much
> >higher than this(?)
> >Are there any guides on diagnosing/tuning biztalk you'd
> recommend?
> >
> >Thanks very much in advance,
> >Nick
> >.
> >

Relevant Pages

  • Re: Adapter Error on non-default host
    ... Mine had to do with some custom adapters dying _only_ when moved to the non-default BizTalk host. ... Mine worked fine on the 'old' web soap service generated. ... When your issue originally came up, did things work okay on the default host for the BizTalk group but not on other hosts in the group, or did it fail in all cases? ... since my issue only pops up when the adapter is associated with the non-default host. ...
    (microsoft.public.biztalk.general)
  • Thread shortage - performance recommendations please
    ... Is there any reason you are not using the inbuild Biztalk ... have a separate host for your Soap send adapter. ... competing with SOAP send adapter for the same threadpool. ...
    (microsoft.public.biztalk.general)
  • Re: Adapter Error on non-default host
    ... The issue would be idepenet of which host you used. ... Mine worked fine on the 'old' web soap service generated. ... host for the BizTalk group but not on other hosts in the group, ... used in the soap adapter for schema validation faulted and threw this. ...
    (microsoft.public.biztalk.general)
  • RE: Errors on Activating Receives
    ... For most polling type adapters there is an error threshold, ... Sql Adapter errors out 5 times in a row, BizTalk will disable that recieve ... it appears that if the stored procedure ...
    (microsoft.public.biztalk.general)
  • RE: Very odd behaviour of our receivehost (bts2006 R2)
    ... I know biztalk heavily relies on AD... ... It's not the isolated receive host, it's the 'normal' receive host that is ... receivehost after that and still this sometimes doesn't help, ... It's my impression that the adapters I installed (AX2009 biztalk adapter ...
    (microsoft.public.biztalk.general)