blocks|key|1022945|text|我认为使用指定重试计数的方面来注释一个方法会导致更多结构化的代码，尽管它需要一些基础设施编码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1022946|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I think annotating a method with an aspect specifying the retry count would result in more structured code, although it needs some infrastructure coding.

blocks|key|808296|text|这不是一种好的风格，但有时你必须这样做，因为你根本不能改变现有的代码并必须处理它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|808297|我在这个场景中使用了下面的泛型方法。请注意PreserveStackTrace()方法，它有时在重新抛出的场景中非常有用。|offset|length|808298|public+static+void+RetryBeforeThrow<T>(Action+action,+int+retries,+int+timeout)+where+T+:+Exception
{
++++if+(action+==+null)
++++++++throw+new+ArgumentNullException("action",+string.Format("Argument+'{0}'+cannot+be+null.",+"action"));

++++int+tries+=+1;

++++do
++++{
++++++++try
++++++++{
++++++++++++action();
++++++++++++return;
++++++++}
++++++++catch+(T+ex)
++++++++{
++++++++++++if+(retries+<=+0)
++++++++++++{
++++++++++++++++PreserveStackTrace(ex);
++++++++++++++++throw;
++++++++++++}

++++++++++++Thread.Sleep(timeout);
++++++++}
++++}
++++while+(tries%2B%2B+<+retries);
}

///+<summary>
///+Sets+a+flag+on+an+<see+cref="T:System.Exception"/>+so+that+all+the+stack+trace+information+is+preserved+
///+when+the+exception+is+re-thrown.
///+</summary>
///+<remarks>This+is+useful+because+"throw"+removes+information,+such+as+the+original+stack+frame.</remarks>
///+<see+href="http://weblogs.asp.net/fmarguerie/archive/2008/01/02/rethrowing-exceptions-and-preserving-the-full-call-stack-trace.aspx"/>
public+static+void+PreserveStackTrace(Exception+ex)
{
++++MethodInfo+preserveStackTrace+=+typeof(Exception).GetMethod("InternalPreserveStackTrace",+BindingFlags.Instance+%7C+BindingFlags.NonPublic);
++++preserveStackTrace.Invoke(ex,+null);
}|code-block|syntax|javascript|808299|你可以这样称呼它：|808300|RetryBeforeThrow<SqlException>(()+=>+MethodWhichFails(),+3,+100);|808301|entityMap|0|LINK|mutability|MUTABLE|url|http://weblogs.asp.net/fmarguerie/archive/2008/01/02/rethrowing-exceptions-and-preserving-the-full-call-stack-trace.aspx^0|0|L|K|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@$D|Y|E|Z|1|10]]|A|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|13|8|@]|9|@]|A|$I|J]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

It's not good style, but sometimes you have to do it, because you simply can't change existing code and have to deal with it.

I am using the following generic method for this scenario. Note the <a href="http://weblogs.asp.net/fmarguerie/archive/2008/01/02/rethrowing-exceptions-and-preserving-the-full-call-stack-trace.aspx" rel="noreferrer">PreserveStackTrace()</a> method, which can sometimes be very helpful in a re-throw scenario.

<pre><code>public static void RetryBeforeThrow&lt;T&gt;(Action action, int retries, int timeout) where T : Exception
{
 if (action == null)
 throw new ArgumentNullException("action", string.Format("Argument '{0}' cannot be null.", "action"));

 int tries = 1;

 do
 {
 try
 {
 action();
 return;
 }
 catch (T ex)
 {
 if (retries &lt;= 0)
 {
 PreserveStackTrace(ex);
 throw;
 }

 Thread.Sleep(timeout);
 }
 }
 while (tries++ &lt; retries);
}

/// &lt;summary&gt;
/// Sets a flag on an &lt;see cref="T:System.Exception"/&gt; so that all the stack trace information is preserved 
/// when the exception is re-thrown.
/// &lt;/summary&gt;
/// &lt;remarks&gt;This is useful because "throw" removes information, such as the original stack frame.&lt;/remarks&gt;
/// &lt;see href="http://weblogs.asp.net/fmarguerie/archive/2008/01/02/rethrowing-exceptions-and-preserving-the-full-call-stack-trace.aspx"/&gt;
public static void PreserveStackTrace(Exception ex)
{
 MethodInfo preserveStackTrace = typeof(Exception).GetMethod("InternalPreserveStackTrace", BindingFlags.Instance | BindingFlags.NonPublic);
 preserveStackTrace.Invoke(ex, null);
}
</code></pre>

You would call it like that:

<pre><code>RetryBeforeThrow&lt;SqlException&gt;(() =&gt; MethodWhichFails(), 3, 100);
</code></pre>

blocks|key|808376|text|将相关代码拉出到它自己的方法中，然后使用递归。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|808377|伪代码：|808378|try
{
++++doDatabaseCall();
}
catch+(exception+e)
{
++++//Check+exception+object+to+confirm+its+the+error+you've+been+experiencing+as+opposed+to+the+server+being+offline.
++++doDatabaseCall();
}|code-block|syntax|javascript|808379|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Pull the relevant code out into its own method, then use recursion.

Pseudo-code:

<pre><code>try
{
 doDatabaseCall();
}
catch (exception e)
{
 //Check exception object to confirm its the error you've been experiencing as opposed to the server being offline.
 doDatabaseCall();
}
</code></pre>

blocks|key|1023144|text|我的sql可重试枚举如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1023145|SqlConnectionBroken+=+-1,
SqlTimeout+=+-2,
SqlOutOfMemory+=+701,
SqlOutOfLocks+=+1204,
SqlDeadlockVictim+=+1205,
SqlLockRequestTimeout+=+1222,
SqlTimeoutWaitingForMemoryResource+=+8645,
SqlLowMemoryCondition+=+8651,
SqlWordbreakerTimeout+=+30053|code-block|syntax|javascript|1023146|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

My enum of retryables for sql looks like this:

<pre><code>SqlConnectionBroken = -1,
SqlTimeout = -2,
SqlOutOfMemory = 701,
SqlOutOfLocks = 1204,
SqlDeadlockVictim = 1205,
SqlLockRequestTimeout = 1222,
SqlTimeoutWaitingForMemoryResource = 8645,
SqlLowMemoryCondition = 8651,
SqlWordbreakerTimeout = 30053
</code></pre>

blocks|key|1023212|text|您可以简单地使用SqlConnectionStringBuilder属性来重试sql连接。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1023213|var+conBuilder+=+new+SqlConnectionStringBuilder("Server=.;Database=xxxx;Trusted_Connection=True;MultipleActiveResultSets=true");+conBuilder.ConnectTimeout+=+90;+conBuilder.ConnectRetryInterval+=+15;+conBuilder.ConnectRetryCount+=+6;|offset|length|style|CODE|1023214|注意：-需要.Net+4.5或更高版本。|1023215|entityMap^0|0|0|6G|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

You can simply use SqlConnectionStringBuilder properties to sql connection retry.

<code>var conBuilder = new SqlConnectionStringBuilder("Server=.;Database=xxxx;Trusted_Connection=True;MultipleActiveResultSets=true");
conBuilder.ConnectTimeout = 90;
conBuilder.ConnectRetryInterval = 15;
conBuilder.ConnectRetryCount = 6;</code>

Note:- Required .Net 4.5 or later.

I have a method that calls a SQLServer function to perform a free text search against a table. That function will occasionally on the first call result in a SQLException: "Word breaking timed out for the full-text query string". So typically I want to retry that request because it will succeed on subsequent requests. What is good style for structuring the retry logic. At the moment I have the following:

<pre><code>var retryCount = 0;
var results = new List&lt;UserSummaryDto&gt;();
using (var ctx = new UsersDataContext(ConfigurationManager.ConnectionStrings[CONNECTION_STRING_KEY].ConnectionString))
{
 for (; ; )
 {
 try
 {
 results = ctx.SearchPhoneList(value, maxRows)
 .Select(user =&gt; user.ToDto())
 .ToList();
 break;
 }
 catch (SqlException)
 {
 retryCount++;
 if (retryCount &gt; MAX_RETRY) throw;
 }
 }
}

return results;
</code></pre>

What is good C# coding style for catching SQLException and retrying

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个方法，它调用SQLServer函数对表执行自由文本搜索。该函数偶尔会在第一次调用时导致SQLException：“全文查询字符串的断字超时”。因此，通常我希望重试该请求，因为它将在后续请求中成功。什么是构建重试逻辑的好风格。目前我有以下几点：var retryCount = 0;var results = ne...

问对于捕获SQLException和重试，什么是好的C#编码风格
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问对于捕获SQLException和重试，什么是好的C#编码风格EN