Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We have a service (A) which Calls another WCF service (B).
Service B has the default values of
<serviceThrottling
maxConcurrentCalls="16"
maxConcurrentSessions="10"
maxConcurrentInstances="26" />
Service A can spawn up to 150 threads, which some of them can call service B.
what happens if service A calls service B with more than the max amount of concurrent connections?
Does service B (WCF) throws them away or stores them in a queue?
The client is blocked until a connection becomes available.
Of course, this behavior indicates the existence of another queue, holding waiting connection requests. I assume that queue would have its own threshold, so once there are a maximum number of waiting connections, further incoming requests would be thrown away. (This is just conjecture on my part, I don’t know where this theoretical queue is configured. …..Somebody?).
I actually experienced a problem in my automated tests where connections were not getting dropped, and this ultimately resulted in my system hanging because the threshold was reached.
https://stackoverflow.com/a/4031284/25216