Friday, May 16, 2008

BizTalk SOAP Adapter - Consuming Remote Web Services Bottleneck

This morning I was told by my colleague that he found hundreds of instances running in the BizTalk Server and from the look of it, most of them are the send port SOAP adapter instances.

We have an orchestration which consumes a web services, so the first thing that came to my mind is that it's gotta be the web services which can not handle the load.

I was thinking that there's gotta be hundreds of concurrent calls to the web services, then i tried to open up the Performance Counter -> ASP.NET Apps v1.1.4322 -> Requests Executing for the particular web services, i was surprised to see that there are only 2 requests executing concurrently :|

Then my other colleage told me that there's a settings in the machine.config file for this, to limit the numbers of call to particular connection.

<add address="*" maxconnection="2">
<add address = "" maxconnection = "5" />
<add address = "" maxconnection = "2" />
<add address = "" maxconnection="12">

After changing this settings to a higher value, the instances were getting completed gradually and not building up anymore :)

You can find more about this at : / BizTalk 2006 Server Documentation -> SOAP Adapter Configuration and Tuning Parameters

However, in the BizTalk 2006 Server Documentation, it states that the default is 20 where .Net Framework Documentation states only 2.

Hope this helps anyone with the same issue ;)


vitamin b said...

I am a network Engineer. This article has helped me a lot in order to manage the server.The explanation given in the article is really great.

Post a Comment