gpt4 book ai didi

c# - 线程中止留下僵尸事务和损坏的 SqlConnection

转载 作者:可可西里 更新时间:2023-11-01 03:10:28 25 4
gpt4 key购买 nike

我觉得这种行为不应该发生。场景如下:

  1. 启动一个长时间运行的 sql 事务。

  2. 运行sql命令的线程被中止(不是我们的代码!)

  3. 当线程返回托管代码,SqlConnection 的状态是“关闭”——但交易是仍然在 sql server 上打开。

  4. 可以重新打开 SQLConnection,你可以尝试调用回滚交易,但它没有效果(不是我期望的这种行为。关键是没有办法访问数据库上的事务并将其回滚。)

问题很简单,线程中止时事务没有正确清理。这是 .Net 1.1、2.0 和 2.0 SP1 的问题。我们正在运行 .Net 3.5 SP1。

这里有一个示例程序可以说明这个问题。

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;

using System.Data.SqlClient;
using System.Threading;

namespace ConsoleApplication1
{
class Run
{
static Thread transactionThread;

public class ConnectionHolder : IDisposable
{
public void Dispose()
{
}

public void executeLongTransaction()
{
Console.WriteLine("Starting a long running transaction.");
using (SqlConnection _con = new SqlConnection("Data Source=<YourServer>;Initial Catalog=<YourDB>;Integrated Security=True;Persist Security Info=False;Max Pool Size=200;MultipleActiveResultSets=True;Connect Timeout=30;Application Name=ConsoleApplication1.vshost"))
{
try
{
SqlTransaction trans = null;
trans = _con.BeginTransaction();

SqlCommand cmd = new SqlCommand("update <YourTable> set Name = 'XXX' where ID = @0; waitfor delay '00:00:05'", _con, trans);
cmd.Parameters.Add(new SqlParameter("0", 340));
cmd.ExecuteNonQuery();

cmd.Transaction.Commit();

Console.WriteLine("Finished the long running transaction.");
}
catch (ThreadAbortException tae)
{
Console.WriteLine("Thread - caught ThreadAbortException in executeLongTransaction - resetting.");
Console.WriteLine("Exception message: {0}", tae.Message);
}
}
}
}

static void killTransactionThread()
{
Thread.Sleep(2 * 1000);

// We're not doing this anywhere in our real code. This is for simulation
// purposes only!
transactionThread.Abort();

Console.WriteLine("Killing the transaction thread...");
}

/// <summary>
/// The main entry point for the application.
/// </summary>
[STAThread]
static void Main(string[] args)
{
using (var connectionHolder = new ConnectionHolder())
{
transactionThread = new Thread(connectionHolder.executeLongTransaction);
transactionThread.Start();

new Thread(killTransactionThread).Start();

transactionThread.Join();

Console.WriteLine("The transaction thread has died. Please run 'select * from sysprocesses where open_tran > 0' now while this window remains open. \n\n");

Console.Read();
}
}
}
}

有一个Microsoft Hotfix targeted at .Net2.0 SP1 that was supposed to address this , 但我们显然有更新的 DLL (.Net 3.5 SP1) 与此修补程序中列出的版本号不匹配。

谁能解释这种行为,以及为什么 ThreadAbort 仍然没有正确清理 sql 事务? .Net 3.5 SP1 是否不包含此修补程序,或者此行为在技术上是否正确?

最佳答案

由于您将 SqlConnection 与池一起使用,因此您的代码永远无法控制关闭连接。游泳池是。在服务器端,当连接真正关闭(套接字关闭)时,挂起的事务将回滚,但是通过池,服务器端永远不会看到连接关闭。没有关闭连接(通过套接字/管道/LPC 层的物理断开连接或通过 sp_reset_connection 调用),服务器无法中止挂起的事务。所以它真的归结为连接没有得到正确释放/重置的事实。我不明白您为什么要尝试通过显式线程中止解雇来使代码复杂化并尝试重新打开已关闭的事务(这将永远 起作用)。您应该简单地将 SqlConnection 包装在 using(...) block 中,隐含的 finally 和连接 Dispose 即使在线程中止时也会运行。

我的建议是保持简单,放弃花哨的线程中止处理并将其替换为普通的“使用” block (using(connection) {using(transaction) {code; commit () }}

当然,我假设您不将事务上下文传播到服务器中的不同范围(您不使用 sp_getbindtoken 和 friend ,并且您不注册分布式事务)。

这个小程序显示了 Thread.Abort 正确地关闭了一个连接并且事务被回滚了:

using System;
using System.Data.SqlClient;
using testThreadAbort.Properties;
using System.Threading;
using System.Diagnostics;

namespace testThreadAbort
{
class Program
{
static AutoResetEvent evReady = new AutoResetEvent(false);
static long xactId = 0;

static void ThreadFunc()
{
using (SqlConnection conn = new SqlConnection(Settings.Default.conn))
{
conn.Open();
using (SqlTransaction trn = conn.BeginTransaction())
{
// Retrieve our XACTID
//
SqlCommand cmd = new SqlCommand("select transaction_id from sys.dm_tran_current_transaction", conn, trn);
xactId = (long) cmd.ExecuteScalar();
Console.Out.WriteLine("XactID: {0}", xactId);

cmd = new SqlCommand(@"
insert into test (a) values (1);
waitfor delay '00:01:00'", conn, trn);

// Signal readyness and wait...
//
evReady.Set();
cmd.ExecuteNonQuery();

trn.Commit();
}
}

}

static void Main(string[] args)
{
try
{
using (SqlConnection conn = new SqlConnection(Settings.Default.conn))
{
conn.Open();
SqlCommand cmd = new SqlCommand(@"
if object_id('test') is not null
begin
drop table test;
end
create table test (a int);", conn);
cmd.ExecuteNonQuery();
}


Thread thread = new Thread(new ThreadStart(ThreadFunc));
thread.Start();
evReady.WaitOne();
Thread.Sleep(TimeSpan.FromSeconds(5));
Console.Out.WriteLine("Aborting...");
thread.Abort();
thread.Join();
Console.Out.WriteLine("Aborted");

Debug.Assert(0 != xactId);

using (SqlConnection conn = new SqlConnection(Settings.Default.conn))
{
conn.Open();

// checked if xactId is still active
//
SqlCommand cmd = new SqlCommand("select count(*) from sys.dm_tran_active_transactions where transaction_id = @xactId", conn);
cmd.Parameters.AddWithValue("@xactId", xactId);

object count = cmd.ExecuteScalar();
Console.WriteLine("Active transactions with xactId {0}: {1}", xactId, count);

// Check count of rows in test (would block on row lock)
//
cmd = new SqlCommand("select count(*) from test", conn);
count = cmd.ExecuteScalar();
Console.WriteLine("Count of rows in text: {0}", count);
}
}
catch (Exception e)
{
Console.Error.Write(e);
}

}
}
}

关于c# - 线程中止留下僵尸事务和损坏的 SqlConnection,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/6219298/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com