Minimizing Connection Pool errors in SQL Azure

re: Minimizing Connection Pool errors in SQL Azure

pwinant — Wed, 26 Sep 2012 21:34:56 GMT

@Rowan Miller - Well, actually that is the same error we're getting. I just didn't post the entire error message. The full error is:

System.Data.SqlClient.SqlError: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An established connection was aborted by the software in your host machine.)

And that is (supposedly) the exact error message the reliability patch is supposed to fix. But it's not working for us, so I've had to implement retry logic around all our database calls.

re: Minimizing Connection Pool errors in SQL Azure

Rowan Miller — Tue, 25 Sep 2012 18:21:39 GMT

@pwinant - Some info from folks on the providers team...

The reliability update fixes a different issue with different associated error message ("A transport-level error has occurred when sending the request to the server"). For more info, please refer to KB support.microsoft.com/.../2533523.

The issue you are having seems to be related to an idle or just a valid non-pooled connection and in this case, the Reliability Update is ineffective.

re: Minimizing Connection Pool errors in SQL Azure

pwinant — Tue, 25 Sep 2012 15:01:13 GMT

I've installed the reliability patch and I'm still getting the exact same "An established connection was aborted by the software in your host machine" error. This is on Windows Server 2003 R2 64-bit. Is there any way to verify the patch was installed correctly? Like a version number on the sql client file or something?

re: Minimizing Connection Pool errors in SQL Azure

Matt — Wed, 28 Mar 2012 05:36:50 GMT

Oh, and here is the link: data.uservoice.com/.../2426525-automatically-perform-retry-logic-for-sql-azure

re: Minimizing Connection Pool errors in SQL Azure

Matt — Wed, 28 Mar 2012 05:36:33 GMT

Hi Diego! My feature request is up to 18 votes now at the time of writing. It's the top feature request for the "Azure" keyword. Any chance this will be implemented soon? Cheers, Matt

re: Minimizing Connection Pool errors in SQL Azure

Diego B Vega — Mon, 12 Dec 2011 02:42:18 GMT

@Matt: Thanks for the feedback! For the long term, we expect successive improvements to the server and lower levels of the client stack (like the one Luiz described in this post) to reduce the need for retry logic significantly. For the shorter term however, we are thinking of ways to package the existing retry patterns in such ways that you don’t need to intersperse them with all your EF data access code. I take the opportunity to invite you to vote for the existing feature request at http://ef.mswish.net (use “Azure” in the search box).

re: Minimizing Connection Pool errors in SQL Azure

Matt — Fri, 02 Dec 2011 01:25:40 GMT

When will EF include SQL Azure retry logic under the hood, without the developer having to wrap every query with the retry logic? Any visibility into this feature would be greatly appreciated. Thanks and keep up the great work.

re: Minimizing Connection Pool errors in SQL Azure

Diego B Vega — Thu, 17 Nov 2011 11:09:32 GMT

@Ken: There are some blog posts with recommendations on how to apply retry logic with EF in SQL Azure scenarios, e.g.:

blogs.msdn.com/.../sql-azure-and-entity-framework-connection-fault-handling.aspx

The principles are generally applicable but you might want to adapt the patterns described in the article depending on the interception points available in the specific framework you are using.

re: Minimizing Connection Pool errors in SQL Azure

Diego B Vega — Thu, 17 Nov 2011 11:00:33 GMT

@Bikram: This improvement to SqlClient helps with the reliability of connections to SQL Azure independently of whether you are using EF.

re: Minimizing Connection Pool errors in SQL Azure

Bikram Sahoo — Wed, 16 Nov 2011 06:04:39 GMT

How to resolve this issue if we are not using EF.