Tuesday, March 06, 2012 1:45 PM
We have a web service that keeps increasing in CallsOutstanding during load test. When the test stops CallsOutstanding flats out, but does not reset - ever.
We're calling numerous other web services in the same load test and we have no such issue with any of them.
Setting a timeout for the web service has no effect at all - there CallsOutstanding will still rise and never time out or reset.
Any suggestion as to what can be wrong? We are using Named pipes binding.
Wednesday, March 07, 2012 6:58 AMModerator
Not sure what reasons cuase this issue, if you are using netnamedpipebinding for your WCF service, then you need to config the maxConnections (the default is 10) attribute properly, How did you host your WCF service? Here is a similar article to which you can refer.
Wednesday, March 07, 2012 7:33 AM
Hi there Peter and thanks for responding!
We are hosting the web services using IIS 7 on windows
We have done adjustments to maxConnections, but it does´t
affect this issue.
I would assume the number of CallsOutstanding for the
service in question would reset after the load test stops no matter what
maxConnections is set to - but it just keeps hanging for a long time.
We´re still working on this issue - the weird thing is
that all our other services are behaving properly. It´s just this particular
Tuesday, March 20, 2012 3:17 AM
Is there any difference for the configuration of this web service from others?
Can you extract this service out to a test project and try without any affect from other services?
If the issue still exists, could you paste your service here including the configurations?
Tuesday, March 20, 2012 8:10 AM
We found the issue at last. It turned out that when an
exception occurred in the initialization of the web service call, the call
would be left hanging forever. In other words, we didn't handle the exception
Thanks for the input guys!
- Marked As Answer by Peter pi - MSFTModerator Tuesday, April 10, 2012 2:41 AM