Shulou(Shulou.com)06/02 Report--

This article mainly explains the "case analysis of WCF data volume". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "case analysis of WCF data quantity".

When testing the concurrency of WCF data and starting 40 client processes at the same time, the IIS server returns a 403 error when it comes to time-consuming service processing. The exception information is as follows:]

System.ServiceModel.Security.MessageSecurityException: System.Net.HttpWebRequest.GetResponse ()

System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply (TimeSpan timeout)

Server stack trace:

System.ServiceModel.Channels.HttpChannelUtilities.ValidateAuthentication (HttpWebRequest request, HttpWebResponse response

WebException responseException, HttpChannelFactory factory)

System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse (HttpWebRequest request

HttpWebResponse response, HttpChannelFactory factory, WebException responseException)

System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.

WaitForReply (TimeSpan timeout) System.ServiceModel.Channels.RequestChannel.Request (Message message, TimeSpan timeout)

System.ServiceModel.Dispatcher.RequestChannelBinder.Request (Message message, TimeSpan timeout)

System.ServiceModel.Channels.ServiceChannel.Call (String action, Boolean oneway, ProxyOperationRuntime operation, Object [] ins, Object [] outs, TimeSpan timeout)

System.ServiceModel.Channels.ServiceChannel.Call (String action, Boolean oneway, ProxyOperationRuntime operation, Object [] ins, Object [] outs)

System.ServiceModel.Channels.ServiceChannelProxy.InvokeService (IMethodCallMessage methodCall, ProxyOperationRuntime operation)

System.ServiceModel.Channels.ServiceChannelProxy.Invoke (IMessage message)

Exception rethrown at [0]:

System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage (IMessage reqMsg, IMessage retMsg)

System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke (MessageData& msgData, Int32 type)

Terminal.ViolationService.IViolationService.QueryVioImg (String vioSeq)

Terminal.ViolationService.ViolationServiceClient.QueryVioImg (String vioSeq), terminal.Program.Main (String [] args)

Error messages for the amount of WCF data are monitored in various ways, but none of these error calls reach WCF, and there are no errors in all places where WCF is monitored and in the TraceLog of WCF. Then pull out the * * magic weapon wireshark, and you can't see any errors when grabbing the package. The client requests the server, and then IIS returns the 403 error and reports the above exception.

So the WCF service is deployed under the iis6 of Win2003server. In this way, there will be no errors when the program runs properly. So I checked the cause of the error caused by IIS5.1. It turns out that it is the number of connections of IIS5.1. So it is summarized as follows:

At the same time, several aspects have been modified:

The number of TCP connections for 1.windowsXP SP3, changed to 512. (there are special tools to crack it.)

2.WCF data volume sessions, calls and instances

Thank you for your reading, the above is the content of "WCF data example Analysis". After the study of this article, I believe you have a deeper understanding of the problem of WCF data example analysis, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.