Hi Alex. The hack couldn't be easily ported. And since the EJB Timer implementation in JBoss is quite limited to handle huge amounts of timers we now decided against it. So we are back to the JobExecutor, even if we extended it so execute the jobs via SLSB. Using the JobExecutor also means removing JMS from the game for async stuff, so everything remaining was the EJB3 SLSB :-/ So maybe it makes more sence to really move these stuff to jbpm 4 and create a working solution there. It is a bit a mess with the enterprise stuff not used in esb vs. JobExecutor scaling better than the enterprise stuff :-/ Cheers Bernd View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209632#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...