[英]How do I get accurate Exception stack in WCF Task-based Operation
我正在使用WCF IErrorHandler接口来捕获和记录WCF服务的服务器端的错误。 但是,传递给HandleError和ProvideFault的异常的StackTrace搞砸了:
at System.ServiceModel.Dispatcher.TaskMethodInvoker.InvokeEnd(Object instance,Object []&outputs,IAsyncResult result)at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeEnd(MessageRpc&rpc)at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage7(MessageRpc&rpc) )......还有更多
我在堆栈跟踪中看到随机的Dispatcher方法并不奇怪,但我想我会在堆栈顶部看到自己的方法。
我已经确定这只会发生在看起来像的操作上
[OperationContract]
public Task<int> MyOperation()
{
throw new ApplicationException("test");
}
看起来像这样的服务有一个适当的堆栈跟踪供我记录:
[OperationContract]
public int MySyncOperation()
{
throw new ApplicationException("test");
}
作为一个FYI,这是错误处理程序方法的样子:
public class MyErrorHandler : IErrorHandler
{
public bool HandleError(Exception error)
{
//variable 'error' has wrong stack trace if exception sourced from Task<int> operation
return false;
}
public void ProvideFault(Exception error, MessageVersion version, ref Message fault)
{
//variable 'error' has wrong stack trace if exception sourced from Task<int> operation
}
}
请注意,异常类型和消息是正确的,所以就好像他们错误地在某处使用'throw ex'而不仅仅是'throw'重新抛出我的异常;
有没有办法从IErrorHandler方法之一获取正确的异常堆栈跟踪?
我最终使用以下自定义操作调用程序解决了这个问题。 我唯一的目标是使用正确的堆栈跟踪记录错误,因此最终被抛出的错误会保留较差的堆栈跟踪。
public class ErrorLoggingOperationInvokerFacade : IOperationInvoker
{
private readonly IOperationInvoker _invoker;
private readonly ILog _log;
public ErrorLoggingOperationInvokerFacade(IOperationInvoker invoker, ILog log)
{
_invoker = invoker;
_log = log;
}
public object[] AllocateInputs()
{
return _invoker.AllocateInputs();
}
public object Invoke(object instance, object[] inputs, out object[] outputs)
{
return _invoker.Invoke(instance, inputs, out outputs);
}
public IAsyncResult InvokeBegin(object instance, object[] inputs, AsyncCallback callback, object state)
{
return _invoker.InvokeBegin(instance, inputs, callback, state);
}
public object InvokeEnd(object instance, out object[] outputs, IAsyncResult result)
{
var task = result as Task;
if (task != null && task.IsFaulted && task.Exception != null)
{
foreach (var error in task.Exception.InnerExceptions)
{
_log.Log(error);
}
}
return _invoker.InvokeEnd(instance, out outputs, result);
}
public bool IsSynchronous { get { return _invoker.IsSynchronous; } }
}
它可以附加您的服务类或方法的属性:
public class LogErrorsAttribute : Attribute, IServiceBehavior, IOperationBehavior
{
public void ApplyDispatchBehavior(ServiceDescription serviceDescription, ServiceHostBase serviceHostBase)
{
foreach (var operation in serviceHostBase.Description.Endpoints.SelectMany(endpoint => endpoint.Contract.Operations))
{
if (!operation.Behaviors.Any(b => b is LogErrorsAttribute))
operation.Behaviors.Add(this);
}
}
public void ApplyDispatchBehavior(OperationDescription operationDescription, DispatchOperation dispatchOperation)
{
dispatchOperation.Invoker = new ErrorLoggingOperationInvokerFacade(dispatchOperation.Invoker, WcfDependencyManager.ResolveLogger());
}
public void Validate(OperationDescription operationDescription) { }
public void ApplyClientBehavior(OperationDescription operationDescription, ClientOperation clientOperation) { }
public void AddBindingParameters(OperationDescription operationDescription, BindingParameterCollection bindingParameters) { }
public void Validate(ServiceDescription serviceDescription, ServiceHostBase serviceHostBase) { }
public void AddBindingParameters(ServiceDescription serviceDescription, ServiceHostBase serviceHostBase, Collection<ServiceEndpoint> endpoints, BindingParameterCollection bindingParameters) { }
}
以前我在IErrorHandler
接口的实现中记录了错误,但此时堆栈跟踪已经搞砸了。 我试图修改操作调用程序以使用正确的堆栈跟踪抛出异常,但我从来没有让它正常工作。 出于某种原因,我的自定义故障异常变成了通用故障异常,因此我放弃了这种方法。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.