多线程Windows服务中的多个同时SQL连接超时 [英] Multiple Simultaneous SQL Connection Timeouts In Multithreaded Windows Service

查看：131 发布时间：2020/5/13 21:18:27 sql-server multithreading connection-timeout

本文介绍了多线程Windows服务中的多个同时SQL连接超时的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

我有一个用VS 2010(.NET 4.0)开发的多线程Windows服务，该服务可以具有数个线程到几十个线程，每个线程都通过Internet从速度较慢的服务器中检索数据，然后使用本地数据库记录此数据(因此该过程受Internet约束，而不受LAN或CPU约束).

I have a multithreaded Windows Service I've developed with VS 2010 (.NET 4.0) which can have anywhere from a few to a few dozen threads, each retrieving data from a slow server over the Internet and then using a local database to record this data (so the process is Internet-bound, not LAN or CPU bound).

以一定的规律性，我同时从多个线程中收到以下错误的泛洪/突发/突发事件:

With some regularity, I am getting a flood/flurry/burst of the following error from several threads simultaneously:

System.Data.SqlClient.SqlException(0x80131904):超时已过期.在操作完成之前已经过了超时时间，或者服务器没有响应.

System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

此错误的调用堆栈通常为:

The call stack for this error is typically:

在System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)

at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)

在System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)

at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)

在System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection externalConnection，DbConnectionFactory connectionFactory)

at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)

在System.Data.SqlClient.SqlConnection.Open()

at System.Data.SqlClient.SqlConnection.Open()

我没有在连接字符串中指定连接超时，并且该数据库中还有其他应用程序和进程正在运行.有没有人遇到过这种行为，如果可以，可以采取什么措施来防止这种情况发生?

I'm not specifying a Connection Timeout in the connection string, and there are other applications and processes working in this database. Has anyone come across this kind of behavior and if so what was done to prevent it?

我的数据访问层中最常用的方法是这样的，而我所有其他DAL方法都遵循相同的方法:

The most commonly-called method in my data access layer looks like this, and all my other DAL methods follow the same approach:

using (SqlConnection con = new SqlConnection(GetConnectionString()))
using (SqlCommand cmd = new SqlCommand("AddGdsMonitorLogEntry", con))
{
    cmd.CommandType = CommandType.StoredProcedure;

    /* setting cmd.Parameters [snipped] */

    // We have been getting some timeouts writing to the log; wait a little longer than the default.
    cmd.CommandTimeout *= 4;

    con.Open();

    cmd.ExecuteNonQuery();
}

非常感谢！

编辑

考虑到在镜像环境中发生的这种情况，我确实应该提到所讨论的数据库是镜像的.在SSMS中以无自动故障转移(同步)的高安全性"模式将其标记为主体，同步".

Given comments about this occurring in mirrored environments, I should indeed mention that the database in question is mirrored. It's marked in SSMS as "Principal, Synchronized", in "High safety without automatic failover (synchronous)" mode.

编辑5/26/11

我在SQL Server日志中看不到任何指示任何问题的信息. (我无权访问该服务器上的Windows事件查看器，但我已要求某人来找我.)

I am seeing nothing in the SQL Server logs to indicate any problems. (I don't have access to the Windows Event Viewer on that server, but I've asked for someone to look for me.)

多线程Windows服务中的多个同时SQL连接超时 [英] Multiple Simultaneous SQL Connection Timeouts In Multithreaded Windows Service

问题描述

推荐答案

相关文章

数据库最新文章

热门教程

热门工具

登录关闭

多线程Windows服务中的多个同时SQL连接超时 [英] Multiple Simultaneous SQL Connection Timeouts In Multithreaded Windows Service

问题描述

推荐答案

相关文章

数据库最新文章

热门教程

热门工具

登录 关闭

登录关闭