your observations are correct: anonymous wrote : | 1.-CommandExecutorThread is not the way to go for me, because it | | consumes the messages in a single thread, so, a Task with... | Indeed there were problems with the command executor thread. Even on a standard java platform (for which it was intended) this was not good enough. We merged the timers and messages into jobs as the basis for our scheduler and message service targetted for the standard java platform. And now we're finishing this rewrite. Multiple concurrent threads should now be supported. Also the jobs will all be executed in a separate transaction. anonymous wrote : | I've also seen that there's a org.jbpm.msg.jms package that seems to | | be an effort to implement just this, a MessageService JMS | | implementation. But it seems it's under construction | Indeed. That is under construction. Currently we are trying to set up a test environment for this in HEAD of CVS. see jpdl/test. that is a sub project in which i want to set up the server side tests with cactus to have a test environment for our JMS implementation of the message service and for our EJB Timer implementation of our scheduler service. All help in setting up this test environment and testing the our JMS implementation of the MessageService is welcome ! Check out jboss/configuration for configuring your jboss and jpdl/test for the test environment that i was going to set up. Can you get the JMS based message service impl running in jboss ? How would you improve what we have in HEAD of cvs today in module jbpm.3 ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3970095#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...