这有助于应用程序避免全局死锁。
因此运行并发线程时,出现了死锁。
同时,还可能出现死锁的情况。
收集整个数据库的死锁事件数据。
db2dlock:用于检测死锁。
该工具还执行死锁检测。
数据库识别出死锁事件。
要尽量避免的锁影响是挂起、超时和死锁。
The effects of locks that you always want to minimize are suspension, timeout, and deadlock.
按照死锁的定义,在这种情况下会发生死锁。
In this situation, the deadlock occurred according to the deadlock definition.
即使数据源支持xa事务,还会有死锁的可能。
Even if the datasource supports XA transactions, there is a possibility of deadlock.
死锁事件异常,用于帮助确定发生死锁的时间。
Deadlock event exception, which is used to help investigate when deadlocks have occurred.
这个图必须是无环的,以避免造成调度上的死锁。
The graph must be acyclic to avoid program scheduling deadlocks.
它减少了资源分配,还减少了出现死锁情况的机会。
It reduces resource allocation and reduces the chance of deadlock scenarios.
EDEADLK:如果继续请求,则会出现资源死锁。
EDEADLK — a resource deadlock would occur if the request continued.
不幸的是,这里仍旧存在另一个潜在的问题,叫做死锁。
Unfortunately, there's another potential problem looming, called a deadlock.
因为每个线程都在等候对方持有的锁,所以就发生了死锁。
Because each thread is waiting for a lock held by the other, a deadlock occurs.
当两个(或以上)线程相互等待别的线程时就会出现死锁。
A deadlock happens when two (or more) threads are each stuck waiting for another.
这样命名的原因在于该构造的相位有序性和死锁预防属性。
The name comes from the construct's phase-ordering and deadlock-avoidance properties.
未重视这些限制会造成应用程序或JVM中出现间断性死锁。
Failing to honor these restrictions can lead to intermittent deadlock within the application or the JVM as a whole.
在整个应用程序中,总是按相同次序访问资源可以最小化死锁。
Minimize deadlocks by always accessing resources in the same order, throughout the application.
尤其是潜在的竞态条件和死锁会突然间成为最令人头疼的问题。
Specifically, problems such as race conditions and deadlocks that lie dormant could suddenly become major problems.
这种特性特别适用于检测死锁、锁竞争、内存泄漏和循环线程。
It's particularly useful for detecting symptoms of deadlocks, lock contention, memory leaks, and cycling threads.
然而,即使是在最好的情况下,这个架构仍然会引起死锁问题。
However, even in a best-case scenario, this architecture can cause deadlock issues.
—但结果几乎总是正确的:更少的死锁和更加适合生产的代码。
But the results are almost always more correct: fewer deadlocks and more production-safe code.
为了避免出现死锁,您必须连接所有必需的控制输入和数据输入。
To avoid a deadlock you must connect all required control inputs and data inputs.
这一模式还可以帮助您免除后端系统使用事务时引起的任何死锁。
This pattern also helps to avoid any deadlocks in case the backend system USES transactions.
为了改善应用程序的并发性,您需要找到引起死锁的sql语句。
In order to improve an application's concurrency, you need to figure out which SQL statements are causing the deadlocks.
运行多个ADMIN_COPY_SCHEMA过程会导致死锁。
Running multiple ADMIN_COPY_SCHEMA procedures results in deadlocks.
建模不恰当的事件处理程序可能导致死锁和由于锁导致长时间等待。
Improperly modeled event handlers may lead to deadlock situations or long wait times caused by locks.
锁升级、锁超时和死锁将表明系统或应用程序中存在某些潜在问题。
The lock escalations, lock timeouts and deadlocks will indicate some potential problems in your system or application.
应用推荐