WCF Service in ASP.NET application generating intermittent 404 errors -
This problem has defeated my efforts on Google, so here goes. We were having trouble getting data from a WCF service (just look at the data, so we enabled it for HTTP GET requests). In every, while it traces a 404. stack will come back once WCF appears in the not mix - StaticFileHandler appears to be trying to service it.
I have created a sample WCF service on ASP.NET 3.5 SP1 and am able to reproduce the issue. This is my sample service - At this point only the differences from stock WCF are enabled for AspNetCompatibilityRequirements and WebScript and HTTP GET: [AspNetCompatibilityRequirements (RequirementsMode = AspNetCompatibilityRequirementsMode.Allowed)] Public Category Service1: IService1 {Public String DoWork (String Ultimate 1) {System.Threading.Thread.Sleep (150); Return "bar"; }} [Service Contract] Public Interface ISS1 1 ([OperationContract] [WebGet] String Dovers (String Param 1);}
Service Config:
& Lt; service name = "namespace.Service1" & gt; Endpoint behaviorConfiguration = "WebSpreadEnited" address = "http: //LocationHost: 2961 / SCC / Service 1.svc" Binding = "WebHTPBinding" Contract = " Namespace I.isis 1 "& gt; / endpoint & gt; & lt; / Service & gt;
Behavioral Config:
& lt ; Behaviors & gt; endpointBehaviors & Gt; & lt; transaction name = "WebScriptEnabled"> ; EnableWebScript /> & lt; / behaviour & gt; & lt; / endpointBehaviors & gt; & gt; / behavior & gt;
My node is aspNetCompatibilityEnabled = "true">, but otherwise everything is quite OOB. I have no optimization on WebHttpBinding at all.
If I were on F5 VS 2008 Created in the web server and using the hit hit, I will continue to hit this with the request already, in a 404. It will result even in a lightweight load (7-10 requests simultaneously), Give me a wick There will be a total of 404 errors.
If I do not leave anything load again and run my test again, then I can easily make 50 requests simultaneously without any I can go to the error.
My actual service is much more complex than this, but to show this behavior, I can get (almost) the stock sample, as if there is a problem related to structure I have activated the WCF diagnosis and tracing but shows anything in logs (not unexpected since WCF stack trace is not in when 404 occurs).
I hope that I am doing something wrong and I have not searched for frame bug. My production environment is IIS6 and displays the behavior similar to my development server.
Comments
Post a Comment