As part of our debug code, we built in some deadlock detection logic — for example, logic that detects and reports layering violations.
我们在调试代码中构建了一些死锁检测逻辑——例如，检测和报告分层违规的逻辑。
Because each thread is waiting for a lock held by the other, a deadlock occurs.
因为每个线程都在等候对方持有的锁，所以就发生了死锁。
The utility also performs deadlock detection.
该工具还执行死锁检测。
In addition, it provided an example showing how to find the SQL statements involved in one deadlock situation by analyzing the traces.
另外，给出了一个例子，演示如何通过分析跟踪找到一个死锁情况所涉及的sql语句。
On the other hand, using synchronization inappropriately or excessively can lead to other problems, such as poor performance and deadlock.
另一方面，不当或过度地使用同步会导致其它问题，比如性能很差和死锁。
It reduces resource allocation and reduces the chance of deadlock scenarios.
它减少了资源分配，还减少了出现死锁情况的机会。
The database recognizes a deadlock event.
数据库识别出死锁事件。
It prevents a common form of deadlock that occurs when multiple sessions are reading, locking, and potentially updating resources later.
防止当多个会话在读取、锁定以及随后可能进行的资源更新时发生常见的死锁。
Currently, modules are provided to perform basic analysis functions for common JVM problems such as deadlock, hang, crash, memory conditions, and so on.
目前，提供了用于对诸如死锁、挂起、崩溃、内存情况等常见JVM问题执行基本分析功能的模块。
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的整个过程，让我们来了解一个死锁场景。
This specific tradeoff involves a choice between two bad results: deadlock the program or fail to protect the state of a critical resource.
这个特定的折衷是对两种糟糕结果的选择：程序死锁，还是不再保护重要资源的状态。
However, even in a best-case scenario, this architecture can cause deadlock issues.
然而，即使是在最好的情况下，这个架构仍然会引起死锁问题。
The answer is that lock timeout reporting builds partly on functionality delivered by deadlock event monitor code.
答案是构建锁定超时报告需要用到死锁事件监视器代码交付的功能。
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.
要想了解如何利用死锁来创建挂起的示例，请参见死锁示例。
Unfortunately, there's another potential problem looming, called a deadlock.
不幸的是，这里仍旧存在另一个潜在的问题，叫做死锁。
However, the second lesson is that it is not necessarily possible to see the deadlock inside the code.
然而，第二个教训是，不可能看到代码里面的死锁。
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事务，还会有死锁的可能。
This section shows us the threads that are involved in the deadlock and the locks that they're holding and waiting for.
这一节向我们展示了死锁中包含的线程，以及它们持有的锁和正在等候的锁。
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.
要尽量避免的锁影响是挂起、超时和死锁。
Failing to honor these restrictions can lead to intermittent deadlock within the application or the JVM as a whole.
未重视这些限制会造成应用程序或JVM中出现间断性死锁。
Optimistic transaction locking is generally preferred for its performance characteristics and reduced likelihood of deadlock situations.
乐观事务锁定通常以其高性能和死锁发生可能性较低的特点而被首选使用。
Collecting deadlock event data for the whole database.
收集整个数据库的死锁事件数据。
应用推荐