You're right about the meaning of locking the process instance. There's a method that wraps that code for you: GraphSession.lockProcessInstance().
I'm convinced there's a way around this problem, that uses locks and fresh data from the database, and does not require spawning yet another thread to resignal. I need to experiment a bit, tough. Could you zip your project files and send the archive to me by e-mail? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911793#3911793 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911793 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user