Within AS 5.1.0 and JBM 1.4.3, I'm curious how the various pools interact. When I have an EJB 3 application with stateless session beans that enqueue a message and it gets dequeued by an EJB 3 MDB, what pools are actually being used? In my specific case, everything is within the VM, so I have a servlet calling the SSB, which enqueues a message, and an MDB consumes the message. So, what appears to be happening is the thread pool in the servlet container runs the servlet that calls the SSB, and the SSB call, since its in VM stays executing on that thread (http thread pool), and then when the message is enqueued from the SSB, it is running on the JCA WorkManager thread (inflow), and when its dequeued from the MDB its on the JCA WorkManager thread as well, and I don't see that the thread pool for JBM is being used, but maybe it is. Also, in looking through the documentation, there appears to be two pools for JBM. One is the TCP connection pool, controlled in the remoting-bisocket-service.xml with the JBM_clientMaxPool setting, which would seem to only be used if the client was remote, and the documentation states a clientMaxPool which seems to be an actual thread pool for execution, but I don't find it in the actual configuration anywhere. So, are either of those two pools actually used in my example case? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240058#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...