I created a custom ClientMessageInspector by implementing IClientMessageInspector. I did this for logging purposes. This works fine but if the load to the service is getting to high, it seems that a deadlock occures (at least no responses will be returned
from the service). After checking my code again and again I got sure that there is no reason within my ClientMessageInspector. Because of this i tried to add another class implementing IEndpointBehavior (in this case the ClientCredentials by adding the <clientCredentials></clientCredentials>
tag to my custom behavior in web.config) to see if the problem exists, too. And the same happened again. I tested this by using SoapUI, creating a load test and setting the number of threads to 5. The interesting thing about was that all worked if i used 4
threads (in both cases, my custom inspector and the ClientCredentials). If no client behavior is injected the problem does not occure at all. Any ideas?
View Complete Post