In jBPM 3.1, multiple scheduler threads query and execute timers without synchronization, leading to duplicate executions. In 3.2, this issue is effectively being addressed through a lock mechanism at the database level. You should be able to run multiple job executor threads. This mechanism is still under test, tough. Let us know if you find any problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009747#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...