I use WCF in a rather complex environment. One behavior that I observed was what I did to name a cold start. When I first start the client that calls the service, there seem to be a lot of failure in the first calls. For example, I can watch the first one say that ten calls go through, and then the next 200 calls fail once. I speak with the service asynchronously. Then the service starts and responds normally. I see that this is the endpoint of the (potentially) problem, not the problem with the operation, since all the different operations will fail. It seems like there is a lock and endpoints and reset itself, and then this is normal, although I have no evidence to support this.
There are no errors on the server side. Client-side logs show many of the following exceptions:
System.ServiceModel.CommunicationException: the server did not provide a meaningful response; this can be caused by a contract mismatch, a premature disconnection of the session, or an internal server error.
I considered the possibility of introducing a smoothing algorithm to equalize service calls, since there are a lot of them at startup. Has anyone else seen this behavior? Thanks.
Steve
EDIT: The service is hosted on a Windows service.
EDIT: Thanks for the guys comments.
From the very beginning, I found that the numbers in different queues are quite high. I have some hard-won knowledge on how to scale WCF services. I allow 2048 concurrent connections. I installed listenBackLog etc.
1000 , , , . , JIT, . , .