按照死锁的定义，在这种情况下会发生死锁。
In this situation, the deadlock occurred according to the deadlock definition.
死锁也会发生在单独的线程中。
经验告诉我们，这需要2条sql语句，并且UPDATE应该在SELECT语句之前执行；否则，当并发增多时，可能会发生死锁。
Conventional wisdom states that this requires 2 SQL statements, and that the UPDATE ought to be done prior to the SELECT; otherwise deadlocks may occur as concurrency increases.
如果中介原语的行为错误(例如，DB查询元素发生死锁)，则流的执行也会发生死锁；通过扇入超时不能缓解此问题。
If a mediation primitive is badly behaved, for example, if a DB Lookup primitive is deadlocked, the execution of the flow is also deadlocked; this situation is not mitigated by the Fan In timeout.
另外，应用程序间可能会发生更多死锁(因为它们都等待数量有限的表锁)，这会导致事务被回滚。
Additionally, there may be more deadlocks between applications (because they are all waiting on a limited number of table locks), which will result in transactions being rolled back.
当使用JBossCache 1 .x，我们在从数据库读取数据并将其放到JBossCache区域中，有时会遇到性能问题，甚至还会发生死锁。
With JBossCache 1.x we would run into performance and sometimes even deadlock issues when reading data from the database and putting that into the JBossCache region.
此输入将永远不会出现，因此join将一直等待缺少的输入而无法执行。在此情况下，很明显会发生死锁。
This input can never come and thus the join will wait forever for the missing input and will not execute-an obvious deadlock situation.
例如，在出现等待leak、过量同步或死锁时会发生hung线程，因此hung线程问题包含这三种场景。
For example, because a hung thread might occur when a wait leak, excessive synchronization, or a deadlock scenario takes place, the hung thread problem consists of three scenarios.
使用锁定还有一些其他危险，如死锁(当以不一致的顺序获得多个锁定时会发生死锁)。
Using locks has some other hazards as well, such as deadlock (which can happen when multiple locks are acquired in an inconsistent order).
如果线程正在等待另一个线程开始或完成，也会发生死锁。
Deadlocks can also occur if a thread is waiting for another thread to start or finish.
但哲学家就餐问题的本质是我不知道什么时候会发生死锁或饥饿。
But the nature of Dining Philosophers problem is I never know when the Dead-lock or starvation will happen.
如果线程已经得到锁，会发生死锁。
如果线程已经得到锁，会发生死锁。
应用推荐