所以我有一个 WCF 服务,其中有一个 Process() 方法。此方法从一个表中读取一个字节数组(一个文件),然后基本上将该文件中的数据放入多个表中。它只是迭代每一行。在生产环境一个月以来,它运行良好。现在突然间,它间歇性地抛出这个错误:
System.InvalidOperationException:与当前连接关联的事务已完成但尚未释放。必须先释放事务,然后才能使用连接执行 SQL 语句。
可能有帮助的事情:
大约两周前,我们更换了生产网络和数据库服务器。这个错误是在我们搬家之后才出现的。当我们使用旧服务器时,我从未遇到过这个问题。但问题是,这个错误并不是在前 9-10 天发生的。现在它突然且间歇性地发生。我上传了大文件(1k-2.5k 行)并且它们运行良好,并且对于具有 200 行的小得多的文件会出现此错误!有时服务可以完美地处理同一个文件。
代码片段:(大了很多,但是重复了类似的操作)
using (var scope = new TransactionScope())
{
// loop through each row/invoice
foreach (var row in Rows)
{
Invoice invoice = (Invoice)CreateObjectWithConstantData(typeof(Invoice), doc, applicationName);
invoice = (Invoice)FillObjectWithUserData(invoice, row, -1, -1, string.Empty);
invoice.InvoiceNumber = InvoiceDBImpl.SaveInvoice(invoice, processFileRequest.RunId);
if (invoice.InvoiceNumber == Guid.Empty)
{
throw new DataAccessException(string.Format(Messages.ErrorSavingInvoice, invoice.ReceiptId, invoice.ProductID));
}
}
}
堆栈跟踪之一:
at System.Data.SqlClient.TdsParser.TdsExecuteRPC(_SqlRPC[] rpcArray, Int32 timeout, Boolean inSchema, SqlNotificationRequest notificationRequest, TdsParserStateObject stateObj, Boolean isCommandProc)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at System.Data.Linq.SqlClient.SqlProvider.Execute(Expression query, QueryInfo queryInfo, IObjectReaderFactory factory, Object[] parentArgs, Object[] userArgs, ICompiledSubQuery[] subQueries, Object lastResult)
at System.Data.Linq.SqlClient.SqlProvider.ExecuteAll(Expression query, QueryInfo[] queryInfos, IObjectReaderFactory factory, Object[] userArguments, ICompiledSubQuery[] subQueries)
at System.Data.Linq.SqlClient.SqlProvider.System.Data.Linq.Provider.IProvider.Execute(Expression query)
at System.Data.Linq.DataContext.ExecuteMethodCall(Object instance, MethodInfo methodInfo, Object[] parameters)
at Tavisca.TramsFileService.DataAccess.TramsDBDataContext.SaveTramsPayment(Nullable`1 paymentDate, String paymentType, Nullable`1 totalAmount, String bankAccount, String paymentMethod, String branch, String remarks, String creditCardLast4, String payeeName, String profileNumber, Nullable`1& paymentId)
at Tavisca.TramsFileService.DataAccess.PaymentDBImpl.<>c__DisplayClass1.<SavePayment>b__0(TramsDBDataContext dc)
at Tavisca.TramsFileService.DataAccess.SystemDataContext.PerformOperation(Action`1 action)
at Tavisca.TramsFileService.DataAccess.PaymentDBImpl.SavePayment(Payment payment)
at Tavisca.TramsFileService.Core.TramsFileController.ProcessFile(ProcessFileRQ processFileRequest)
at Tavisca.TramsFileService.ServiceImplementation.TramsFileServiceImpl.ProcessFile(ProcessFileRQ processFileRequest)
我已经通过一些链接:
- Link 1 https://stackoverflow.com/questions/11248943/the-transaction-must-be-disposed-before-the-connection-can-be-used-to-execute-sq
- Link 2 http://thecodesaysitall.blogspot.in/2012/04/long-running-systemtransactions.html
- Link 3 https://stackoverflow.com/questions/11453066/error-the-transaction-associated-with-the-current-connection-has-completed-but
他们都建议增加 machine.config 上的超时,但我不确定为什么它有时有效而有时不起作用。这不应该是一致的吗?