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.
Similar posts to check out:
- July 7, 2011 -- Automatic eTag Management with WCF Web API Message Handlers (0)
... - May 26, 2011 -- Troubleshooting WCF Performance – Part 1 (0)
More related details on Dustin's post - WCF scales up slowly with bursts of work.... - 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...
Tags: .wcf
