Interested to Buy Any Domain ? << Click Here >> for more details...
what is the differencees between work manager and executequeue?
- 2 Answers
- 13575 Views
- iFlex, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / kamal sastry
1.Unlike execute queues, all WorkManagers share a common
thread pool and a priority-based queue.
2. The size of the
thread pool is determined automatically by the kernel and
resized as needed.
3.WorkManagers become very lightweight, and customers can
create WorkManagers without worrying about the size of the
thread pool.
4.Thread dumps look much cleaner with fewer threads.
In the new model, it is possible to specify different
service-level agreements (SLAs) such as fair shares or
response-time goals for the same servlet invocation
depending on the user associated with the invocation.
5.In earlier releases, each servlet or RMI request was
associated with a dispatch policy that mapped to an execute
queue.Requests without an explicit dispatch policy use the
server-wide default execute queue. In WebLogic Server 9.0,
requests are still associated with a dispatch policy but
are mapped to a WorkManager instead of to an execute queue.
6.Execute queues are always global whereas
WorkManagers are always application scoped. Even
WorkManagers defined globally in the console are
application scoped during runtime. This means that each
application gets into own runtime instance that is distinct
from others, but all of them share the same characteristics
like fair-share goals.
7. Another advantage is Thread Count Self-tuning. One of the
major differences between execute queues and the
new thread scheduling model is that the thread count does
not need to be set. In earlier releases, customers defined
new thread pools and configured their size to avoid
deadlocks and provide differentiated service. It is quite
difficult to determine the exact number of threads needed
in production to achieve optimal throughput and avoid
deadlocks. WebLogic Server 9.0 is self-tuned, dynamically
adjusting the number of threads to avoid deadlocks and
achieve optimal throughput subject to concurrency
constraints. It also meets objectives for differentiated
service. These objectives are stated as fair shares and
response-time goals as explained in the next section.
| Is This Answer Correct ? | 5 Yes | 1 No |
Answer / king
Just to add in above points:
Execute Queue concepts used till 8.1+ weblogic releases.
Work Manager came from Weblogic 9+
| Is This Answer Correct ? | 2 Yes | 2 No |
Why does jmssession.createtopic or jmssession.createqueue fail to create a destination in wls jms 6.1 (it worked in 5.1)? : BEA Weblogic
What is a non-durable topic subscriber?
What are the steps required to setup the oracle instance for os authentication?
How can I set deployment order for applications?
Why would a client application use jta transactions?
What is the difference between jndi lookup(), list(), listbindings(), and search()?
Which are the benefits of mdb (message driven beans) over standard jms consumers? : BEA Weblogic
What happens when database down in weblogic
How should you type cast a remote object? Why?
What is config.xml?
What are the causes of having ociw32.dll error in the database of web logic server?
What is the difference between multicast and unicast?
Core Java 
