HTTP请求超时Windows Azure部署 [英] HTTP Request Timeout Windows Azure Deploy

问题描述

我有一个使用WCF服务的MVC 4网站.当我使用VS 2012发布向导部署到Windows Azure时，出现此错误:

I have an MVC 4 website using a WCF service. When I deploy to Windows Azure using the VS 2012 publish wizard, I get this error:

上午10:13:19-对'https://management.core.windows.net/42d4257b-5f38-400d-aac5-2e7acee9597d/services/hostedservices/myapp?embed-detail=true'的HTTP请求具有超过了指定的00:01:00超时.分配给该操作的时间可能是较长超时的一部分.

10:13:19 AM - The HTTP request to 'https://management.core.windows.net/42d4257b-5f38-400d-aac5-2e7acee9597d/services/hostedservices/myapp?embed-detail=true' has exceeded the allotted timeout of 00:01:00. The time allotted to this operation may have been a portion of a longer timeout.

清理项目并发布几次后，错误消失了.我在做什么错了?

After cleaning the project and publishing a few times, the error goes away. What am I doing wrong?

推荐答案

无论何时从VS计算机开始发布过程，都会首先建立一个SSL隧道，一旦创建了该隧道，程序包便会从您的计算机传输到Windows Azure门户.第一的.上载完成后，您将看到结果通知回发到发布结果"窗口，这就是这种情况.

Whenever you start publish process from VS machine, a SSL tunnel is established first and once the tunnel is created, the package is transferred from your machine to Windows Azure Portal first. After the upload is completed, you will see the result notifications are posted back to Publish result windows and that is how it happens.

对于您来说，建立SSL隧道进行安全软件包传输的时间比正常时间长，这可能是由于计算机与Windows Azure管理门户之间的网络延迟.出于安全原因，创建隧道较小窗口的时间；如果未创建连接，则重试周期将再次启动该过程，即使失败，也会收到失败消息，欢迎您.这可能是由于双方或双方的流量过大所致.因此，这主要是与网络相关的问题，而不是Windows Azure的特定问题，因为经过一段时间的连续尝试，您可以上载软件包.

In your case, the time to build the SSL tunnel doe secure package transfer is longer then normal, this could be because of network latency between your machine and the Windows Azure Management Portal. For security reason the time to create the tunnel smaller windows and if the connection is not created, the retry cycle starts the process again and even if that fails you are greeted with the failure message. This could be caused by excessive traffic on either side or both sides. So this is mainly a networking related issue rather then specific to Windows Azure as after some time successive tries, you could upload your package.

在这种故障/情况下，您可以运行网络捕获实用程序，即 netmon ， wireshark ，并查看失败和成功期间所花费的时间不同的转移.这将帮助您了解潜在的延迟问题.

In such failure/situation, you can run network capture utilities i.e netmon, wireshark, and see the time taken during failure and success to see the different in various transfer. This will help you to understand the underlying delaying issues.

这篇关于HTTP请求超时Windows Azure部署的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！