Azure Sql和Azure App Service-连接问题 [英] Azure Sql and Azure App Service - connection issues
问题描述
All of a sudden I started getting these errors:
连接尝试失败，因为已连接一方在一段时间后未正确响应，或者由于连接的主机未能响应而导致建立连接失败.
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
建立与SQL Server的连接时发生了与网络相关或特定于实例的错误.服务器未找到或无法访问.验证实例名称正确，并且已将SQL Server配置为允许远程连接. (提供者:TCP提供程序，错误:0-连接尝试失败，因为一段时间后连接方未正确响应，或者连接建立由于连接主机未能响应而失败.)
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)
没有新内容代码已在几周内部署，它开始于昨晚发生，我不知道该怎么办.
No new code was deployed in weeks, it started happening last night and I have no idea what to do.
推荐答案
DimaSF，得知您遇到此问题，我们深感抱歉.
DimaSF, we are sorry to hear you are encountering this issue.
首先要看的是:
- 您的计算机可以建立的出站连接数量受到限制.由于您尚未对设置进行任何更改，因此这就是我要解决的问题.快速解决方案是将您的网站扩展到下一个 尺寸.如果使用的是S1实例，请考虑升级到具有更多可用出站连接的S2实例.有关更多信息，请参见此 链接.扩大规模可能只是一个创可贴.您可能需要考虑实现连接池或其他代码缓解措施，以避免达到此限制
- There is a limit on the number of outbound connections that your machine can make. Since you have not made any changes to your setup, this is what I'm leaning towards being the issue. A quick resolution to this would be to scale your site up to the next size. If you are using an S1 instance, consider moving up to an S2 instance, which has more outbound connections available. For more info, please see this link. Scaling up is likely only a band-aid. You may need to consider implementing connection pooling or another code mitigation to avoid hitting this limit
这篇关于Azure Sql和Azure App Service-连接问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
