I've brought this up on the Hibernate forum:
http://forum.hibernate.org/viewtopic.php?t=972301
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029479#4029479
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029479
___
"[EMAIL PROTECTED]" wrote : I sometimes get this issue when I use JBC. Of
course the original stack trace would be completely useless, so instead here is
some random stack trace based on some pseudo-code I wrote based on my
assumptions about the code...
|
|
Steve,
I didn't include the Hi
By the way, in case it helps, here is the Hibernate code that does the same
thing:
SessionFactory factory = new
AnnotationConfiguration().configure().buildSessionFactory();
| TransactionManager txManager =
DummyTransactionManager.getInstance();
| txMa
JBoss Cache version: 1.4.1.SP2
I have been having some problems using Hibernate with JBoss Cache in optimistic
locking mode. During the after-completion phase of the transaction, Hibernate
will, in certain circumstances, call TreeCache.remove.
This causes problems because JBoss Cache sees that
JBoss Cache version: 1.4.1.SP2
This relates to an issue I am having with Hibernate:
http://forum.hibernate.org/viewtopic.php?p=2343598
When I'm using pessimistic locking, the following code will work:
public static void main(String[] args) throws Exception {
| UserTransacti
