When you install SP1 for .NET 3.0 by default that changes the throttling settings you might be use to. You could get into a situation where a number of calls are processed and then they stop with the client eventually timing out. To get around this you either explicitly close your connection (which is a good practice in most cases) or change the serviceThrottling setting in your WCF config.
Other similar posts you might be interested to check out:
- September 21, 2008 -- Avoid using “using()” (0)
The using statement in C#, seems to be quite useful especially to a developer as theoretically, you not have to do anything to release any memory you might have used and the CLR automatically frees up this memory for you.
However, over time, I have had so many issues with it and subtle problems (in certain situations) I am starting to avoid it now.
The two best examples that I can think of are database connection pools and WCF connections. You might think that a “using” statement would clo... - July 21, 2008 -- P2P Code (0)
It took a while for me to get around to this but the P2P Code to go along with my MSDN Article "P2P Programming with WCF and .NET v3.5". I don't know why this code was not available on MSDN in the first place. Any ways, the can be downloaded from here (456.2 KB).... - March 6, 2008 -- Load testing WCF (0)
Someone recently asked about how to load test WCF - apart from the usual things like LoadRunner, VSTS Test Load Agent, etc a couple of other interesting options came up. One is WCF Load Test and the other JMeter. WCF Load Test generates a unit test taking in data from a a trace file along with the relevant WCF proxy or interface. I must admit, JMeter would not have been one of the things that would have come to mind to me in this context, but technically there is nothing stopping from you using...
Tags: .indigo
