本文介绍了等待异步调用引发意外超时异常的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！
问题描述
我正在服务结构应用程序上执行一系列异步调用，有一个长期运行的调用将在5-10分钟后抛出TimeoutException。我的代码类似于：
public class Listener {
private async Task HandleRequestAsync(RestoreRequest request, RestoreWorker worker) {
Response response = await worker.ExecuteAsync(request).ConfigureAwait(false);
}
}
public class RestoreWorker {
public async Task<Response> ExecuteAsync(RestoreRequest request) {
RestoreService restoreService = new restoreService(request);
restoreService.Progress.ProgressChanged += async (sender, info) => await request.UpdateStatusAsync(new State(StateEnum.Running) { ProgressCurrent = info.Current, ProgressTotal = info.Total }).ConfigureAwait(false);
await restoreService.RestoreAsync(request.Id, request.Name).ConfigureAwait(false);
return new Response();
}
public Progress<ProgressInfo> Progress { get; } = new Progress<ProgressInfo>();
}
public class RestoreRequest {
public async Task UpdateStatusAsync(Status status) {
Message message = new Message { Status = status };
await sender.SendAsync(message).ConfigureAwait(false);
}
}
public class RestoreService {
private static readonly IRestoreClient restoreClient = ServiceProxyFactory.CreateServiceProxy<IRestoreClient>(new Uri($"{FabricConfig.ApplicationName}/RestoreClient"));
private async Task <Project> GetProjectByNameAsync(string name){
//return the project
}
private async Task RestoreAsync(string id, string name) {
await restoreClient.RestoreAsync(id, name).ConfigureAwait(false);
}
}
public class RestoreClient : IRestoreClient {
private async Task RestoreAsync(string id, string name) {
Project project = await GetProjectByNameAsync(name).ConfigureAwait(false);
project = await UpdateDbAsync(project.Id).ConfigureAwait(false);
if (project == null) {
throw new Exception("Could not find project.");
}
}
private async Task UpdateDbAsync(string id) {
try {
List<string> input = CreateScripts();
await ExecuteScriptsOnDbAsync(input).ConfigureAwait(false);
} catch (SqlException) {
throw new Exception($"Project with id: '{id}' could not be created.");
}
}
private async Task ExecuteScriptsOnDbAsync(List<string> scripts) {
using (var conn = new SqlConnection(connectionString)) {
try {
await conn.OpenAsync().ConfigureAwait(false);
using (var sqlCommand = new SqlCommand { Connection = conn }) {
sqlCommand.CommandTimeout = SqlCommandCommandTimeout;
foreach (string script in scripts) {
sqlCommand.CommandText = script;
await sqlCommand.ExecuteNonQueryAsync().ConfigureAwait(false);
}
}
} catch (SqlException ex) {
Log.Fatal(ex, $"Cannot execute script on {Name}");
throw;
}
}
}
}
如果方法UpdateTheDBAsync执行时间较长，我将收到TimeoutException
System.AggregateException: One or more errors occurred. ---> System.TimeoutException: This can happen if message is dropped when service is busy or its long running operation and taking more time than configured Operation Timeout.
at Microsoft.ServiceFabric.Services.Communication.Client.ServicePartitionClient`1.<InvokeWithRetryAsync>d__24`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.ServiceFabric.Services.Remoting.V1.Client.ServiceRemotingPartitionClient.<InvokeAsync>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.ServiceFabric.Services.Remoting.Builder.ProxyBase.<InvokeAsync>d__15.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.ServiceFabric.Services.Remoting.Builder.ProxyBase.<ContinueWithResult>d__16`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
at RestoreService.<RestoreAsync>d__14.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable.ConfiguredTaskAwaiter.GetResult()
at RestoreWorker.<ExecuteAsync>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
at Listener.<HandleRequestAsync>d__15.MoveNext()
PS：这段代码过去用来工作
推荐答案
该问题与服务之间的远程处理(ServiceFabric.Services.Remoting)的默认超时5分钟有关。
版本2的远程处理是可用的，根据Microsoft documentation"远程处理V2堆栈执行得更好"。
升级到V2后，解决该问题的一种可能方法是增加超时
new ServiceProxyFactory((c) => new FabricTransportServiceRemotingClientFactory(
new FabricTransportRemotingSettings() {
OperationTimeout = TimeSpan.FromMinutes(30)
})))
但这只会增加超时，而不会完全删除它。
解决该问题的另一种方法是启动一个直接在与远程处理一起使用的服务中处理的工作进程，并等待其完成。这样，解决方案就不会绑定到远程处理超时。例如：
正在替换：
await restoreClient.RestoreAsync(id, name).ConfigureAwait(false);
与
var workerId = StartANewWorker()
JobState jobState;
do {
//poll for the status of the new worker
var workerStatus = GetStatusOfTheWorker(workerId);
await Task.Delay(1000).ConfigureAwait(false);
if (workerStatus == Failed) {
throw new Exception("Something went wrong");
}
} while (workerStatus != Finished);
这篇关于等待异步调用引发意外超时异常的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！