We are having the same problem. Has anyone tried other options like
optimistic-lock="false"
on some of the relationships between token and the other tables? The children relationship
looks suspect in that is a child Token gets removed or added, the version of the parent
Token is incremented. This could possibly cause lots of StaleObjects during transitions in
sub processes say if I understand the data model correctly.
Also, has anyone tried
<class name="Token" table="TOKEN"
optimistic-lock="all">
or
<class name="Token" table="TOKEN"
optimistic-lock="dirty">
thus removing the version column altogether and using the values of columns in memory to
detect a clash?
The Hibernate docs say using a "version" column is preferred but these other
strategies may solve the problem if not elegantly.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197082#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...