Or use this configuration in the client.
<system.net>
<connectionManagement>
<add maxconnection = "200" address ="*" />
</connectionManagement>
</system.net>
Here 200 is the limit from the client
More Related Contents:
- WCF – How to Increase Message Size Quota
- How to Consume WCF Service with Android
- A reference to the dll could not be added
- How to solve “Could not establish trust relationship for the SSL/TLS secure channel with authority”
- Injecting data to a WCF service
- Maximum array length quota
- Difference between web reference and service reference?
- WCF Service Returning “Method Not Allowed”
- Contract-First SOA: Designing Business Domain: WCF
- Is .NET Remoting really deprecated?
- Why is the first WCF client call slow?
- ServiceRoute + WebServiceHostFactory kills WSDL generation? How to create extensionless WCF service with ?wsdl
- Reports in SOA (Business Intelligence & Service Oriented Architecture)
- WCF: Exposing readonly DataMember properties without set?
- How to prevent Visual Studio from launching WcfSvcHost.exe while debugging?
- Calling a webservice that uses ISO-8859-1 encoding from WCF
- replace WCF built-in JavascriptSerializer with Newtonsoft Json.Net json serializer
- Any way to make DataContractJsonSerializer serialize Dictionaries properly?
- WCF Error “Maximum number of items that can be serialized or deserialized in an object graph is ‘65536’”
- Web Services — WCF vs. ASMX (“Standard”)
- WCF service startup error “This collection already contains an address with scheme http”
- WCF error: The caller was not authenticated by the service
- Service has zero application (non-infrastructure) endpoints
- Can I pass non-string to WCF RESTful service using UriTemplate?
- WCF Disable Deserialization Order Sensitivity
- Service reference not generating client types
- How to set keep alive interval for HTTP connection in WCF
- What’s the best way to jSON serialize a .NET DataTable in WCF?
- WCF sessions with a wsHttpBinding and without windows security
- Managing complex Web.Config files between deployment environments