[jboss-dev-forums] [Design of JBoss jBPM] - Re: does optimistic locking always work ?

tom.baeyens@jboss.com do-not-reply at jboss.com
Thu Sep 21 05:01:07 EDT 2006


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#3973189

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973189



More information about the jboss-dev-forums mailing list