1: by using it in a server that provides functionality for this. e.g. if JBoss AS supports
hibernate caching across a cluster jBPM will use that if you configure it to use e.g. the
datasource of your appserver. You should also use ejb timers then instead of the jBPM
timer solution (although both have some issues)
2: If a process is in a certain state and nothing is happening, nothing is locked. If you
have long running actions, make them async. That way nothing is locked either
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192211#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...