Hey folks, when running against SQL Azure it is possible for your connection to fail because you've been throttled (due to high load, etc...) and in that case you get an error like this:
“System.Data.SqlClient.SqlException: The service is currently busy. Retry the request after 10 seconds. Code: 6553965539 A severe error occurred on the current command. The results, if any, should be discarded.” Digging around through the published guidance, we are told we should wrap our database calls in retry logic, disposing of the connection, opening a new one and trying again... but all the examples are of code dealing directly with the ADO.NET objects. (you can see one here if you are interested: http://jonesie.net.nz/2009/11/17/SQLAzureThrottlingRetries.aspx) Does anyone have a suggestion on how to achieve similar results using NHibernate? I've seen a couple of similar questions here already, but the answer seemed to be "fix the problem that is making the connection fail" and in this case it isn't necessarily possible for us to 100% fix the problem (these connection drops may occur, regardless of what our application is doing). -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
