With all of this information, it should be possible to resolve the deadlock.
有了这些信息，就应当可以解决死锁问题了。
This class encapsulates information about each agent involved in a deadlock alert.
这个类用于封装一个死锁中每个代理的相关信息。
Because each thread is waiting for a lock held by the other, a deadlock occurs.
因为每个线程都在等候对方持有的锁，所以就发生了死锁。
The utility also performs deadlock detection.
该工具还执行死锁检测。
If it is constant over time, a probable deadlock or hang could have occurred.
如果它长时间不变，那么很可能是发生了死锁或挂起。
It reduces resource allocation and reduces the chance of deadlock scenarios.
它减少了资源分配，还减少了出现死锁情况的机会。
The database recognizes a deadlock event.
数据库识别出死锁事件。
So the deadlock occurred when concurrent threads were run.
因此运行并发线程时，出现了死锁。
Activating a database starts the logger for logging activity and the deadlock detector for detecting the deadlocks.
数据库的激活将启动日志记录器来记录活动以及启动死锁检测器来检测死锁。
To walk you through the process of using the PDTK, let's look at a deadlock scenario.
为了带领您遍历使用PDTK的整个过程，让我们来了解一个死锁场景。
However, even in a best-case scenario, this architecture can cause deadlock issues.
然而，即使是在最好的情况下，这个架构仍然会引起死锁问题。
With any multithreaded application, there is a risk of deadlock.
任何多线程应用程序都有死锁风险。
Improperly modeled event handlers may lead to deadlock situations or long wait times caused by locks.
建模不恰当的事件处理程序可能导致死锁和由于锁导致长时间等待。
In this situation, the deadlock occurred according to the deadlock definition.
按照死锁的定义，在这种情况下会发生死锁。
EDEADLK — a resource deadlock would occur if the request continued.
EDEADLK：如果继续请求，则会出现资源死锁。
For an example of how to create a hang using a deadlock, see this deadlock example.
要想了解如何利用死锁来创建挂起的示例，请参见死锁示例。
In Figure 5, you can see two resources were involved in the deadlock.
在图5中，可以看到死锁涉及到两个资源。
Unfortunately, there's another potential problem looming, called a deadlock.
不幸的是，这里仍旧存在另一个潜在的问题，叫做死锁。
When a deadlock occurs, it collects information about the applications involved, the SQL statements participating in the deadlock, and the locks causing high contention.
当发生死锁时，这个监控器收集相关应用程序、死锁中的sql语句以及引起高争用的锁的信息。
Even if the datasource supports XA transactions, there is a possibility of deadlock.
即使数据源支持xa事务，还会有死锁的可能。
There is also more chance of deadlock situations occurring.
同时，还可能出现死锁的情况。
In case of a deadlock or lock timeout, this information can be used to present a history of SQL statements that may be involved in the deadlock or lock timeout occurrence.
如果发生死锁或锁定超时，这个信息可用于提供sql语句的历史信息，这些sql语句可能与死锁或锁定超时的发生有关。
The effects of locks that you always want to minimize are suspension, timeout, and deadlock.
要尽量避免的锁影响是挂起、超时和死锁。
因此发生死锁。
In the above example, the deadlock is relatively easy to spot.
在上面的示例中，死锁比较容易发现。
Analyze the lock information from the deadlock report.
根据死锁报告来分析锁信息。
Collecting deadlock event data for the whole database.
收集整个数据库的死锁事件数据。
Db2dlock: For deadlock detection.
db2dlock：用于检测死锁。
Table 1 summarizes the deadlock analysis.
表1总结死锁分析。
Locking trace - deadlock report.
Locking跟踪——死锁报告。
应用推荐