我有以下(简化)Hibernate实体:
@Entity(name = "Foo")
public class Foo {
@Id
@GeneratedValue
public int id;
@OneToOne
public Bar bar;
}
和,
@Entity(name = "Bar")
public class Bar {
@Id
@GeneratedValue
public int id;
@Column
public String field;
@Version
public int version;
}
我在一个看起来大致如下的事务中更新这些实体:
Bar bar = findBar(em);
Foo foo = findFoo(em);
bar.field = "updated value";
if () {
em.remove(foo);
}
em.detach(bar);
em.merge(bar);
请注意,em.remove(foo)有时仅被调用,而bar始终更新.
我偶然注意到ORA-00060:运行应用程序时死锁检测到错误.转储似乎暗示两个死锁的会话被锁定在em.merge(bar)和em.remove(foo)上,但我不明白为什么会出现这种情况.
这段代码怎么会死锁?有没有办法重组它避免死锁?
以下是跟踪中的一些额外信息:
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-00040005-000010dd 73 6557 X 81 6498 X
TX-00010018-000010bd 81 6498 X 73 6557 X
session 6557: DID 0001-0049-000002F5 session 6498: DID 0001-0051-0000030E
session 6498: DID 0001-0051-0000030E session 6557: DID 0001-0049-000002F5
Rows waited on:
Session 6557: obj - rowid = 00004797 - AAAEeXAB4AAADH0BBP
(dictionary objn - 18331, file - 120, block - 12788, slot - 15)
Session 6498: obj - rowid = 00007191 - AAAHGRAB4AAAACBBBo
(dictionary objn - 29041, file - 120, block - 129, slot - 40)
----- Information for the OTHER waiting sessions -----
Session 6498:
program: JDBC Thin Client
application name: JDBC Thin Client, hash value=2546894660
current SQL:
delete from Foo where id=:1
----- Current SQL Statement for this session (sql_id=sfasdgasdgaf) -----
update Bar set field=:1, version=:2 where id=:3 and version=:4