如何在数据库操作中使用tpl [英] how to use tpl with database operation

问题描述

我一直在尝试'parallel.foreach'来选择和更新数据库。我在stacktrace中收到以下错误。我怎样才能解决这个问题？



c＃：

Hi,

I have been trying 'parallel.foreach' to select and update the database. I am getting the following error in stacktrace. How can i resole this?

c#:

Parallel.ForEach(queueList,server =>
                {
                    
                    DataTable dtServerDetails=new DataTable();
                    string selectServerDetailsQuery = @"SELECT * FROM server_details WHERE;";
                    dtServerDetails = sqlObject.SelectCommand(selectServerDetailsQuery)
                       
                });

错误：

error:

Quote：

System.NullReferenceException：对象引用未设置为对象的实例。

at MySql.Data.MySqlClient.MySqlDataReader.Close（）

at MySql.Data.MySqlClient.MySqlConnection.Close（）

System.NullReferenceException: Object reference not set to an instance of an object.
at MySql.Data.MySqlClient.MySqlDataReader.Close()
at MySql.Data.MySqlClient.MySqlConnection.Close()

辩诉给我一个解决方案..



谢谢

Amrutha。

Please provide me a solution..

Thanks
Amrutha.

推荐答案

如果异常跟踪正确，则表示 MySql.Data.MySqlClient.MySqlDataReader 由于某种原因为空。



您没有显示带有对象引用未设置为对象实例消息的异常位置。



不用担心。这是检测和修复的最简单的案例之一。它只是意味着某些引用类型的某个成员/变量通过使用和它的实例（非静态）成员解除引用，这要求此成员/变量为非null，但实际上它似乎为null。只需在调试器下执行它，它将停止抛出异常的执行。在该行上设置一个断点，重新启动应用程序并再次到达这一点。评估下一行中涉及的所有引用，并查看哪一个为null，而不需要为null。解决这个问题之后，修复代码：要么确保将成员/变量正确初始化为非空引用，要么将其检查为null，如果为null，则执行其他操作。



另请参阅：想要在按钮点击时显示下一条记录。但是如果下一条记录功能的条件对象引用没有设置为对象的实例 [ ^ ]。



有时候，你不能在调试器下，由于一个或另一个原因做到这一点。一个这样的原因可能是时机。如果您使用任何形式或并行（TPL，线程），您的错误可能会创建竞争条件。由于这种竞争条件，你的代码执行可能会在一个时序情况下导致一些麻烦而不会导致另一个时间（这是最糟糕的情况，因为它隐藏了问题）。调试可能会改变时间并导致您无法重现问题。请参阅： http://en.wikipedia.org/wiki/Race_condition [ ^ ]。



另一个非常讨厌的案例是当问题仅在调试信息不​​可用时构建软件时才会出现。在这种情况下该怎么办？



在这种情况下，你必须使用更难的方法。首先，你需要确保你永远不会通过静默处理异常来阻止异常的传播（这是开发人员对自己的犯罪，但很常见）。您需要在每个线程的最顶层堆栈帧上捕获绝对所有异常。如果处理类型 System.Exception 的异常，则可以执行此操作。在处理程序中，您需要记录所有异常信息，尤其是 System.Exception.StackTrace ：

http://msdn.microsoft.com/en-us/library/system.exception.aspx [ ^ ]，

http://msdn.microsoft.com/en-us/library/system.exception。 stacktrace.aspx [ ^ ]。



堆栈跟踪只是一个字符串，显示从throw语句到处理程序的异常传播的完整路径。通过阅读，您总能找到目的。对于日志记录，使用类 System.Diagnostics.EventLog ：

http://msdn.microsoft.com/en-us/library/system.diagnostics.eventlog.aspx [ ^ ]。

-SA

If the exception trace is correct, it means that MySql.Data.MySqlClient.MySqlDataReader is null by some reason.

You did not show where the exception with the message "Object reference not set to an instance of an object" is thrown.

Not to worry. This is one of the very easiest cases to detect and fix. It simply means that some member/variable of some reference type is dereferenced by using and of its instance (non-static) members, which requires this member/variable to be non-null, but in fact it appears to be null. Simply execute it under debugger, it will stop the execution where the exception is thrown. Put a break point on that line, restart the application and come to this point again. Evaluate all references involved in next line and see which one is null while it needs to be not null. After you figure this out, fix the code: either make sure the member/variable is properly initialized to a non-null reference, or check it for null and, in case of null, do something else.

Please see also: want to display next record on button click. but got an error in if condition of next record function "object reference not set to an instance of an object"[^].

Sometimes, you cannot do it under debugger, by one or another reason. One such reason could be timing. If you use any form or parallelism (TPL, threads), your bug may create a race condition. Due to this race condition your code execution can lead to some trouble at one timing situation and don't lead to it in another (and this is the worst case, as it hides the problem). Debugging can change timing and cause you to fail to reproduce the problem. Please see: http://en.wikipedia.org/wiki/Race_condition[^].

Another really nasty case is when the problem is only manifested if software is built when debug information is not available. What to do in such cases?

In this case, you have to use the harder way. First, you need to make sure that you never block propagation of exceptions by handling them silently (this is a crime of developers against themselves, yet very usual). The you need to catch absolutely all exceptions on the very top stack frame of each thread. You can do it if you handle the exceptions of the type System.Exception. In the handler, you need to log all the exception information, especially the System.Exception.StackTrace:
http://msdn.microsoft.com/en-us/library/system.exception.aspx[^],
http://msdn.microsoft.com/en-us/library/system.exception.stacktrace.aspx[^].

The stack trace is just a string showing the full path of exception propagation from the throw statement to the handler. By reading it, you can always find ends. For logging, it's the best (in most cases) to use the class System.Diagnostics.EventLog:
http://msdn.microsoft.com/en-us/library/system.diagnostics.eventlog.aspx[^].

Good luck,

—SA

这篇关于如何在数据库操作中使用tpl的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！