我收到了WebException：＆＃34;操作已超时＆＃34;立即在HttpWebRequest.GetResponse（）上

Question

我在多线程环境中大量抓取网页内容。我需要一个可靠的下载程序组件，可以容忍临时服务器故障，连接丢失等。以下是我的代码的样子。

现在，我一遍又一遍地处于一种奇怪的境地：这一切都完美无缺。 10个线程同时拉数据大约10分钟。在那之后，我在调用请求对象的GetResponse方法后立即开始获取超时的WebException。休息一下（让线程入睡）并没有帮助。它只会在我停止应用程序并重新启动它直到接下来的10分钟过去并且问题再次出现时才有帮助。

我已经尝试过但没有任何帮助：

• 通过“using”语句显式关闭/处置响应对象
• 致电请求。在任何地方都可以帮助
• 在ServicePointManager / ServicePoint和WebRequest级别操作超时（延长/缩短超时间隔）
• 操纵KeepAlive属性
• 调用CloseConnectionGroup
• 操纵同时运行的线程的数量

没有任何帮助！所以它似乎是一个错误或至少记录很差的行为。我在谷歌和Stackoverflow上看到了很多关于这个的问题，但是没有完全回答。基本上人们会从上面的列表中提出一些建议。我尝试了所有这些。

    public TResource DownloadResource(Uri uri)
    {
        for (var resourceReadingAttempt = 0; resourceReadingAttempt <= MaxTries; resourceReadingAttempt++)
        {
            var request = (HttpWebRequest)WebRequest.Create(uri);
            HttpWebResponse response = null;
            for (var downloadAttempt = 0; downloadAttempt <= MaxTries; downloadAttempt++)
            {
                if (downloadAttempt > 0)
                {
                    var sleepFor = TimeSpan.FromSeconds(4 << downloadAttempt) + TimeSpan.FromMilliseconds(new Random(DateTime.Now.Millisecond).Next(1000));
                    Trace.WriteLine("Retry #" + downloadAttempt + " in " + sleepFor + ".");
                    Thread.Sleep(sleepFor);
                }
                Trace.WriteLine("Trying to get a resource by URL: " + uri);

                var watch = Stopwatch.StartNew();
                try
                {
                    response = (HttpWebResponse)request.GetResponse();
                    break;
                }
                catch (WebException exception)
                {
                    request.Abort();
                    Trace.WriteLine("Failed to get a resource by the URL: " + uri + " after " + watch.Elapsed + ". " + exception.Message);
                    if (exception.Status == WebExceptionStatus.Timeout)
                    {
                        //Trace.WriteLine("Closing " + request.ServicePoint.CurrentConnections + " current connections.");
                        //request.ServicePoint.CloseConnectionGroup(request.ConnectionGroupName);
                        //request.Abort();
                        continue;
                    }
                    else
                    {
                        using (var failure = exception.Response as HttpWebResponse)
                        {

                            Int32 code;
                            try { code = failure != null ? (Int32)failure.StatusCode : 500; }
                            catch { code = 500; }

                            if (code >= 500 && code < 600)
                            {
                                if (failure != null) failure.Close();
                                continue;
                            }
                            else
                            {
                                Trace.TraceError(exception.ToString());
                                throw;
                            }
                        }
                    }
                }
            }

            if (response == null) throw new ApplicationException("Unable to get a resource from URL \"" + uri + "\".");
            try
            {
                // response disposal is required to eliminate problems with timeouts
                // more about the problem: http://stackoverflow.com/questions/5827030/httpwebrequest-times-out-on-second-call
                // http://social.msdn.microsoft.com/Forums/en/netfxnetcom/thread/a2014f3d-122b-4cd6-a886-d619d7e3140e

                TResource resource;
                using (var stream = response.GetResponseStream())
                {
                    try
                    {
                        resource = this.reader.ReadFromStream(stream);
                    }
                    catch (IOException exception)
                    {
                        Trace.TraceError("Unable to read the resource stream: " + exception.ToString());
                        continue;
                    }
                }
                return resource;
            }
            finally
            {
                // recycle as much as you can
                if (response != null)
                {
                    response.Close();
                    (response as IDisposable).Dispose();
                    response = null;
                }
                if (request != null)
                {
                    //Trace.WriteLine("closing connection group: " + request.ConnectionGroupName);
                    //request.ServicePoint.CloseConnectionGroup(request.ConnectionGroupName);
                    request.Abort();
                    request = null;
                }
            }
        }
        throw new ApplicationException("Resource was not able to be acquired after several attempts.");
    }

Answer 1

我有同样的问题我在互联网上搜索了很多，我有一个解决方案，一次修复线程数。你必须一次控制线程数，我已经开始使用2-3线程一次。 也使用这个ServicePointManager.DefaultConnectionLimit = 200; 这对你很有帮助。