Question

我有一个SoapExtension。它记录了我的所有Web服务请求和响应。我认为项目中有超过一千个webservice调用。我的问题是，如果我的webservice呼叫以超时或像403,404这样的httpexceptions结束，我就无法记录请求。我也需要记录这些异常。

这是我的SoapExtension

public class SoapLogger : SoapExtension
{
    Stream orgStream;
    Stream newStream;
    LogItem logItem;

    // When the SOAP extension is accessed for the first time, the XML Web
    // service method it is applied to is accessed to store the file
    // name passed in, using the corresponding SoapExtensionAttribute.    
    public override object GetInitializer(LogicalMethodInfo methodInfo, SoapExtensionAttribute attribute)
    {
        return 0;
    }

    // The SOAP extension was configured to run using a configuration file
    // instead of an attribute applied to a specific XML Web service
    // method.
    public override object GetInitializer(Type WebServiceType)
    {
        return 0;
    }

    // Receive the file name stored by GetInitializer and store it in a
    // member variable for this specific instance.
    public override void Initialize(object initializer)
    {
        logItem = new LogItem();
    }

    // Save the Stream representing the SOAP request or SOAP response into
    // a local memory buffer.
    public override Stream ChainStream(Stream stream)
    {
        orgStream = stream;
        newStream = new MemoryStream();
        return newStream;
    }

    //  If the SoapMessageStage is such that the SoapRequest or
    //  SoapResponse is still in the SOAP format to be sent or received,
    //  save it out to a file.
    public override void ProcessMessage(SoapMessage message)
    {
        switch (message.Stage)
        {
            case SoapMessageStage.BeforeSerialize:
                break;
            case SoapMessageStage.AfterSerialize:
                WriteOutput();
                break;
            case SoapMessageStage.BeforeDeserialize:
                WriteInput(message);
                break;
            case SoapMessageStage.AfterDeserialize:
                CheckException(message);
                break;
            default:
                throw new Exception("invalid soap stage");
        }
    }

    public void CheckException(SoapMessage message)
    {

        logItem.WebClassName = message.MethodInfo.DeclaringType.FullName;
        logItem.WebMethodName = message.MethodInfo.Name;

        MethodBase method = FindMethod(logItem.WebMethodName);

        logItem.MethodName = method != null ? method.Name : "";
        logItem.ClassName = method != null ? method.DeclaringType.Name : "";

        logItem.Exception = message.Exception != null ? message.Exception.Message : "";

        LogToDB(logItem);
    }

    MethodBase FindMethod(string webMethodName)
    {
        try
        {
            StackFrame[] stackFrames = new StackTrace().GetFrames();

            int i;
            for (i = 0; i < stackFrames.Length; i++)
            {
                if (stackFrames[i].GetMethod().Name == webMethodName) break;
            }
            return i < stackFrames.Length - 1 ? stackFrames[i + 1].GetMethod() : null;
        }
        catch
        {
            return null;
        }
    }

    void LogToDB(LogItem logItem)
    {
        // I am logging logItem to db
    }

    public void WriteOutput()
    {
        newStream.Position = 0;

        logItem.Request = CopyString(newStream);
        logItem.StartTime = DateTime.Now;

        newStream.Position = 0;
        Copy(newStream, orgStream);
        newStream.Position = 0;
    }

    public void WriteInput(SoapMessage message)
    {
        Copy(orgStream, newStream);
        newStream.Position = 0;

        logItem.Response = CopyString(newStream);
        logItem.EndTime = DateTime.Now;

        newStream.Position = 0;
    }

    void Copy(Stream from, Stream to)
    {
        TextReader reader = new StreamReader(from);
        TextWriter writer = new StreamWriter(to);
        writer.WriteLine(reader.ReadToEnd());
        writer.Flush();
    }

    string CopyString(Stream from)
    {
        TextReader reader = new StreamReader(from);
        return reader.ReadToEnd();
    }

}

Answer 1

以下文字可能会帮助您解决问题。

＆＃34; SoapExtension解决方案

解决这个问题的最流行的方法（我到目前为止找到的）是编写一个自定义的SoapExtension子类，它在Web服务请求的不同阶段对您的SoapMessage进行低级访问。响应。当发生未处理的异常时，可以在响应SoapMessage中捕获SoapException（通过Exception属性）。然后，SoapException的InnerException属性包含实际的未处理异常。此时，您可以在出门时记录异常，这样当您从技术支持部门收到该电子邮件时，您就可以继续使用。

但是，如果你曾经开发过真正的面向公众的网络服务（就像我们的网站服务一样），你很快就会认为仅仅记录例外是不够的。通常，您需要对SoapException本身的内容进行更多控制，然后将其发送回调用方。 SoapExtension子类方法使您能够修改SoapException，但是级别非常低。具体来说，它已经被反序列化为其代表性的SOAP错误XML，你必须做一些奇特的流操作来将任何自定义内容插入到该错误中（例如：添加一个detail元素）。在我看来，这是一个黑客，而不是一个非常优雅的解决方案。相反，我们应该在抛出之前更多地控制SoapException。理想情况下，如果我们可以自己创建并抛出SoapException，我们可以更好地控制结果SOAP错误的内容（如故障代码和细节）。那么我们就不必费心去拦截和操纵原始的SOAP消息。＆＃34;

请访问该链接以获取更多信息： http://beyondthispoint.blogspot.co.uk/2008/04/managing-unhandled-exceptions-in-aspnet.html

如何处理SoapExtension中的超时异常

1 个答案: