CallsOutstanding for a certain service increasing during load test and not resetting after test end

Question

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.

Answer 1

Hi,

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.

http://blogs.msdn.com/b/wenlong/archive/2009/02/08/why-only-two-concurrent-requests-for-load-testing.aspx

 

Regards,
Peter

---

Please mark the replies as answers if they help or unmark if not. If you have any feedback about my replies, please contact [e-mail] Microsoft One Code Framework

Answer 2

Hi there Peter and thanks for responding!

We are hosting the web services using IIS 7 on windows
server 2008.

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
one.

Any suggestions?

Answer 3

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?

Answer 4

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
correctly.

Thanks for the input guys!