-
1. Re: Separate Execute Queue in JBOSS
rajesh.gajula May 15, 2007 7:11 AM (in response to rajesh.gajula)Hi,
Can some one answer my query... ?
Is my query so silly or too tough to answer.
-Raj -
2. Re: Separate Execute Queue in JBOSS
weston.price May 15, 2007 7:15 AM (in response to rajesh.gajula)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>
-
3. Re: Separate Execute Queue in JBOSS
patwary_shiva Oct 3, 2007 4:56 PM (in response to rajesh.gajula)we are migrating from weblogic to jboss we have execute queue in weblogic . How do i configure in jboss. Should i
myqueue1
System Threads
<!-- How long a thread will live without any tasks in MS -->
60000
<!-- The max number of threads in the pool -->
10
<!-- The max number of tasks before the queue is full -->
1000
<!-- 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
-->
run
myqueue2
System Threads
<!-- How long a thread will live without any tasks in MS -->
60000
<!-- The max number of threads in the pool -->
10
<!-- The max number of tasks before the queue is full -->
1000
<!-- 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
--> -
4. Re: Separate Execute Queue in JBOSS
danielen Dec 3, 2008 7:54 AM (in response to rajesh.gajula)Any news on this topic? JBoss still doesnt support any form og execution queue or any other method to limit the number of simultaneous rmi calls to a jboss server. We need to limit the peek throughput so that we dont DDOS all of our sub systems (db, external systems etc) that has a limit of how many clients calls they may execute at the same time.
The only solution we have found right now,
pray that we never have any peaks in rmi trafic and that we can handle the normal application load within limits, is not good enough for production.
We are migrating a weblogic application to jboss. Weblogic has execution queues that limit how many simultaneous rmi executions that could happen from all connected clients, and make sure that we always are safe within of the throughput limits of the system.
This is a EJB2 system, using jboss 4.3 eap.
If no solutions in the ejb2 container, does the new ejb3 container support somthing we could use? -
5. Re: Separate Execute Queue in JBOSS
luis.espinal Feb 14, 2009 12:32 AM (in response to rajesh.gajula)Oh my, I'm also coming from a WL point of view, and I have to say I'm extremely surprised JBoss does not support separate execute queues.
OTH, I'm sure some developers that use JBoss as their AS must surely had encounter a situation where resources had to be prioritized (or contained) differently from the rest.
How exactly people manage this? If, for reasons of performance or availability you have to segregate your incoming requests into different queues/thread pools/whatever, how do you guys handle that in JBoss? Do you need to have separate JBoss instances for each group?