That tends to produce deadlocks.

僵局就此产生。

Finalization can also introduce deadlocks.

终结也可能导致死锁。

You also don't have to worry about deadlocks.

也不必担心死锁。

Deadlocks can also happen within a single thread.

死锁也会发生在单独的线程中。

This helps avoid global deadlocks for applications.

这有助于应用程序避免全局死锁。

Cyclic deadlocks through join-fork and join-decision pairs.

因join - fork和join - decision对导致的循环死锁。

The graph must be acyclic to avoid program scheduling deadlocks.

这个图必须是无环的，以避免造成调度上的死锁。

Lock - Number of locks held, deadlocks and lock waits escalations.

LOCK——保存的锁、死锁和锁等待升级的数目。

Running multiple ADMIN_COPY_SCHEMA procedures results in deadlocks.

运行多个ADMIN_COPY_SCHEMA过程会导致死锁。

This is done to avoid deadlocks while working with an empty database.

这样做的目的是避免使用空数据时出现的死锁。

The alternative is to break negotiation deadlocks based on willpower.

而另一种打开谈判僵局的办法是运用你的意志力。

A counter enumerates values that increase, such as the number of deadlocks.

计数器计算增加的值，比如死锁数。

However, it can be a problem when the frequency or percentage of deadlocks is high.

但是当死锁的频率或比例较高时容易出现问题。

A key to breaking deadlocks with principled negotiations is to use objective criteria.

在运用原则谈判法进行谈判的过程中，打开谈判僵局的关键在于使用客观标准。

Deadlock event exception, which is used to help investigate when deadlocks have occurred.

死锁事件异常，用于帮助确定发生死锁的时间。

This pattern also helps to avoid any deadlocks in case the backend system USES transactions.

这一模式还可以帮助您免除后端系统使用事务时引起的任何死锁。

This version of the program demonstrates a common source of deadlocks: programmer stupidity.

这个版本的程序演示了一个产生死锁的一般来源：程序员的错误。

You may experience deadlocks from a database if both methods try to access to the same table.

如果两个方法都试图访问同一张表，您就可能遇到来自数据库的死锁。

But the results are almost always more correct: fewer deadlocks and more production-safe code.

—但结果几乎总是正确的：更少的死锁和更加适合生产的代码。

Minimize deadlocks by always accessing resources in the same order, throughout the application.

在整个应用程序中，总是按相同次序访问资源可以最小化死锁。

Running multiple DB2MOVE commands to copy schemas from one database to another results in deadlocks.

运行多个DB 2 MOVE命令将模式从一个数据库复制到另一个数据库会导致死锁。

As an example, assume there are deadlocks when multiple shoppers log on and register a shop concurrently.

作为例子，我们假定当多个顾客同时登录并注册一个商店时发生死锁。

It's particularly useful for detecting symptoms of deadlocks, lock contention, memory leaks, and cycling threads.

这种特性特别适用于检测死锁、锁竞争、内存泄漏和循环线程。

These can be invaluable for debugging, as they can identify the source of deadlocks or other unexpected behaviors.

这些对调试非常有价值，因为它们能标识死锁或者其他异常行为的来源。

Specifically, problems such as race conditions and deadlocks that lie dormant could suddenly become major problems.

尤其是潜在的竞态条件和死锁会突然间成为最令人头疼的问题。

Activating a database starts the logger for logging activity and the deadlock detector for detecting the deadlocks.

数据库的激活将启动日志记录器来记录活动以及启动死锁检测器来检测死锁。

These problems help us reason about how to ensure that we avoid deadlocks between processes competing for resources.

这些问题帮助我们处理如何确保避免竞争资源的进程之间的死锁。

The lock escalations, lock timeouts and deadlocks will indicate some potential problems in your system or application.

锁升级、锁超时和死锁将表明系统或应用程序中存在某些潜在问题。

This article, the final installment in this four-part series, examines class loader deadlocks and constraint violations.

本文是本系列中的四篇文章的最后一篇，它研究了类装入器死锁和约束违反。

In order to improve an application's concurrency, you need to figure out which SQL statements are causing the deadlocks.

为了改善应用程序的并发性，您需要找到引起死锁的sql语句。