session.load(class, id, LockMode.UPGRADE) or session.lock(processInstance,
LockMode.UPGRADE) results in "SELECT ... FOR UPDATE" on databases that support
pessimistic locking, this will result in a pessimistic lock.
We expose the lock already in the JbpmContext (or in the persistence service, i don't
remember). So users can start adding pessimistic locks themselves whenever they want
to.
But I want to work out a solution/workaround/fix that works by only using optimistic
locking.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973189#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...