本文介绍了WebService错误:{“底层连接已关闭:接收时发生意外错误”}的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在过去一个月我一直在测试一个供应商的Web服务,这是正常的。有一天它开始超时了。设置超时属性之后,我开始收到此响应。我被告知,他们没有做出任何改变,也不能重现我的问题。我也被告知,我们的网络没有改变。

I have been testing a vendors webservice for the past month which was working fine. Then one day it started timing out. After setting the timeout property higher I started getting this response back. I was told that no changes were made on their side and that they could not recreate my issue. I was also told that there was no changes made on our network.

我一直在搜索一两天,但是在我尝试更接近解决方案时,已经证明是无效的。在这一点上,我真的相信这是在他们的尽头,但我的问题是,有没有办法证明更明确的问题是没有使用他们的服务器日志?另一个皱纹在这里让我觉得是他们的问题是他们有另一个webservice,我仍然可以得到有效的回复。

I have been searching around for a day or two here but have proved fruitless on my attempts to get closer to a solution. At this point I truly believe it is on their end but my question is, is there a way to prove more definitively where the issue is short of having their server logs? The other wrinkle here which makes me feel it is their problem is that they have another webservice which I can still get valid responses back from.

我使用fiddler2但我不我知道如果我可以使用请求生成器测试一个webservice,似乎不起作用。

I use fiddler2 but I don't know if I can test a webservice with the request builder, it doesn't seem to work.

我的设置如下我使用visual studio 2008 C#asp。网络参考网络项目。

My setup is as follows I am using visual studio 2008 C# asp.net project with a web reference to this service.

提前非常感谢您的帮助

推荐答案

使用获取网络痕迹。诊断您是否使用HTTPS会很棘手,但它比Fiddler低级,这意味着他们无法声称代理引起问题。

Use Wireshark to get network traces. It'll be tricky to diagnose if you're using HTTPS, but it's lower-level than Fiddler, which means they won't be able to claim that the proxying is causing problems.

基本上,您需要确保请求真的被发送,并且您没有及时得到响应。

Basically, you need to make sure that the request really is being sent, and that you're not getting a response back in time.

这篇关于WebService错误:{“底层连接已关闭:接收时发生意外错误”}的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-24 12:29