There are two possibilities here. First, your database supports optimistic
locking in which case you can specify that in your *-ds.xml file. Second, you
are using Hibernate for persistence in which case it uses optimistic locking by
default unless you can set the optimistic-lock mapping attribut
Many thanks for the reply.
I'm using mysql.
So all I have to do is edit the datasource to make the cache use optimistic
locking ? I probably should have said I meant in the cache ?
Thanks,
Gerry Smith
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246271#424
Which data provider are you using in MySQL? I know that InnoDB does not provide
optimistic locking?
Cache? Nothing like throwing in yet another term. What cache are you thinking
about? Are you perhaps thinking of the caching that Hibernate does, since
Hibernate is used to implement JPA?
The
I was referring to JBoss cache, I think I need to do something like this:
http://www.redhat.com/docs/manuals/jboss/jboss-eap-4.2/doc/cache/Tree_Cache_Guide/Configuration-Sample_XML_Based_Configuration.html
Thanks again,
Gerry Smith
View the original post :
http://www.jboss.org/index.html?modul
- or upgrade to 5.1 and use MVCC, but I had other problems upgrading the app to
5.0.
(obviously I'm getting deadlocks with pessimistic locking)
Gerry Smith
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246290#4246290
Reply to the post :
http://www.jboss.o
