[jboss-user] [JBoss jBPM] - Re: Lock problems after migrating to JBPM 3.2 and Seam 2.0

kukeltje do-not-reply at jboss.com
Wed Sep 19 16:30:21 EDT 2007

afaik, the default node behaviour changed from 'persistent' to 'non persistent'. So signalling is not needed and leads to a duplicate signalling while the node is still 'busy' try removing the process.signal() to see if you get the behaviour you want without the lock.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086321#4086321

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

More information about the jboss-user mailing list