Exception during multiple asynchronous calls to WCF (The message could not be processed...) -

You can not process me "message from a WCF client ..." getting error please help me Is killing

I have a test win app that is brought in the number of asynchronous calls x loop to x . Each asynchronous call instructs their own instances of the WCF proxy and calls a WCF service using that proxy. If x is about 35 or less then all is well. If x > 40 or so, calls completed several fine, but a handful of the refund:

  System.ServiceModel.Security.MessageSecurityException: an insecure or See incorrect internal error for the fault code and extension. --- & gt; System.ServiceModel.FaultException: The message could not be processed. The reason for this is that the action 'http://tempuri.org/IMyService/MakeRequest' is incorrect or because the message contains incorrect or finished security reference token or because there is a mismatch between binding is most likely. The security reference token will be invalid if the channel has been canceled due to service inactivity. To stop the service from canceling the service inactive sessions, extend the time limit on service end point binding ahead of time. --- inner exception stack trace --- server end of the stack trace: at System.ServiceModel.Security.SecuritySessionClientSettings`1.SecurityRequestSessionChannel.ProcessReply (Send reply, TimeSpan timeout, SecurityProtocolCorrelationState correlationState) on System.ServiceModel.Security.SecuritySessionClientSettings`1 .SecurityRequestSessionChannel.Request (messages, timed TimeSpan) (message message System.ServiceModel.Dispatcher.RequestChannelBinder.Request, timed TimeSpan) on System.ServiceModel.Channels.ServiceChannel.Call (string action, Boolean oneway, ProxyOperationRuntime Operation, object [] These, the object [] Execution TimeSpan timed out) System. Sistmkrntaim in: [0] exception rethrown in System.ServiceModel.Channels.ServiceChannelProxy.InvokeService (IMethodCallMessage methodCall, ProxyOperationRuntime operation) (iMessage messages) on ServiceModel.Channels.ServiceChannelProxy.Invoke. Remoting. Proxy. Real Proxy. Handle Return Message (IMSEF Recom, IMSEG E retMsg) on ​​system. time. Remoting. Proxy. RealProxy Private Invoock (MessageData & amp; MsgData, Int32 type) ...  

I am using customer safety and message-side certificates, with message security. I do not find why it runs just a fixed number, then Pux starts throwing an error on the call, which are close to the end of the trend. Also, this error is long before any of my expiration will be reached, which are being installed on the same client and server side:

  & lt; Binding name = "WSHttpBinding_IMyService" closeTimeout = "00: 10: 00" Opantaimaut = "00:10:00" receive timeout = "00:10:00" Bejentaimaut = "00:10:00" ... / ...  

In addition, I am using Service Throttling:

  & lt; ServiceThrottling maxConcurrentCalls = "100" maxConcurrentSessions = "100" />  

Any ideas?

Thank you, Mark.

You get an error when you reach a certain limit on the number of calls and each call will be your own proxy makes.

Therefore the error is related to creation or termination and cleaning proxy.

You have not posted your code, but you may be able to solve the problem again and improve the performance of your code by following these best practices:

One And the problem is that Async WCF calls to make sure that the proxy is not stopped before the async call returns.