On the other approaches page, instead of marking a bean as asynchronous, how about if a thread name was specified for each bean? For the first attempt at parallel deployments, we might start with two execution threads. Beans that have no thread name, execute in a default thread. The other beans will execute in the other named thread. The beans will need to be configured to avoid deadlocks. I prefer this logic to be in the beans as this will help us deal with object lock contention (dealing with lock contention is a different problem but very important to achieve for performance). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238482#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...