Think of jBPM of a convenient way to update your process management database. Refreshing is not the approach you would normally take in an application with multiple concurrent accesses to a database. The thread would either block (pessimistic lock) or receive an exception causing it to retry its work (optimistic lock).
I can think of this solution: introduce a state just before the join, and perform the work in each path without locking. When that returns, lock the process instance and then signal the token. The tradeoff here is, as always, concurrency vs. consistency. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911610#3911610 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911610 ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
