There is no concept of a 'Separate Excecute Queue' in JBoss. All applications (per node) share the same underlying thread pool. These settings can be found in your jboss-service.xml file which resides in the conf directory for your particular node: | | <!-- A Thread pool service --> | <mbean code="org.jboss.util.threadpool.BasicThreadPool" | name="jboss.system:service=ThreadPool"> | <attribute name="Name">JBoss System Threads</attribute> | <attribute name="ThreadGroupName">System Threads</attribute> | <!-- How long a thread will live without any tasks in MS --> | <attribute name="KeepAliveTime">60000</attribute> | <!-- The max number of threads in the pool --> | <attribute name="MaximumPoolSize">10</attribute> | <!-- The max number of tasks before the queue is full --> | <attribute name="MaximumQueueSize">1000</attribute> | <!-- The behavior of the pool when a task is added and the queue is full. | abort - a RuntimeException is thrown | run - the calling thread executes the task | wait - the calling thread blocks until the queue has room | discard - the task is silently discarded without being run | discardOldest - check to see if a task is about to complete and enque | the new task if possible, else run the task in the calling thread | --> | <attribute name="BlockingMode">run</attribute> | </mbean> | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045757#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...