Hi!

We are experiencing serious scaling problems using the BTS 2004 SOAP
adapter. In our current environment, we have load peaks of about 500
concurrent messages which BTS has to send to an IIS based web service.
When BTS tries to send these messages to the web service, the eventlog
(BTS machine) is flooded with the following error message: "There were
not enough free threads in the ThreadPool object to complete the
operation".
Additionally, we get a lot of timeouts. In total, only about 20% of the
messages are delivered successfully.
Searching the internet for the problem, we found the following KB
article which seems to perfectly describe our problem. Obviously, the
BTS Soap adapter is using the .NET framework for sending and receiving
messages but does not implement a queueuing mechanism:
http://support.microsoft.com/defaul...kb;en-us;815637

Setting the thread pool size to 100 (the maximum) is obviously not
enough in our scenario and all experiments on the server (web service)
side did not help either.
The first workaround suggestion from MS (increasing the retires) is not
really helpful, too.

Any ideas?
Microsoft: How about writing a SOAP adapter with internal queueuing???

Thanks for your help,
Roland

[ Post a follow-up to this message ]

Got a solution from Stefan Reinebo. Thanks a lot!

- Create new in-process host.
- Attach SOAP-adapter to the new host.
- Update LowWatermark and Highwatermark (try lwm-10 and hwm-25 for a
start)

You can tune all parameters by using this tool :
http://go.microsoft.com/fwlink/?linkid=30076.



In article <MPG.1bd4beaca3f230f7989682@msnews.microsoft.com>,
roland.jaeger@dmr-consulting.com says...
> Hi!
>
> We are experiencing serious scaling problems using the BTS 2004 SOAP
> adapter. In our current environment, we have load peaks of about 500
> concurrent messages which BTS has to send to an IIS based web service.
> When BTS tries to send these messages to the web service, the eventlog
> (BTS machine) is flooded with the following error message: "There were
> not enough free threads in the ThreadPool object to complete the
> operation".
> Additionally, we get a lot of timeouts. In total, only about 20% of the
> messages are delivered successfully.
> Searching the internet for the problem, we found the following KB
> article which seems to perfectly describe our problem. Obviously, the
> BTS Soap adapter is using the .NET framework for sending and receiving
> messages but does not implement a queueuing mechanism:
> http://support.microsoft.com/defaul...kb;en-us;815637
>
> Setting the thread pool size to 100 (the maximum) is obviously not
> enough in our scenario and all experiments on the server (web service)
> side did not help either.
> The first workaround suggestion from MS (increasing the retires) is not
> really helpful, too.
>
> Any ideas?
> Microsoft: How about writing a SOAP adapter with internal queueuing???
>
> Thanks for your help,
> Roland
>

[ Post a follow-up to this message ]