Related Tasks Related Topics
This server is configured to use execute queues. This method of thread prioritization is provided for backwards compatibility.
Requests to a WebLogic Server instance are placed in an execute queue. Each request is assigned to a thread within the queue that performs the work. You can configure a new WebLogic Server instance to use a default execute queue, weblogic.kernel.default, that contains 15 threads. In addition, WebLogic Server provides two other pre-configured queues:
weblogic.admin.RMI. Because these queues are reserved for communicating with the Administration Console and for administrative traffic, you cannot reconfigure them. Unless you configure additional execute queues and assign applications to them, Web applications and RMI objects use the
weblogic.kernel.defaultexecute queue. When they are available, this page displays current runtime characteristics and statistics for the server's active execute queues.
WebLogic Server provides another method for prioritizing work using Work Managers.
Using Work Managers, the common thread pool changes its size automatically to maximize throughput. The queue monitors throughput over time and based on history, determines whether to adjust the thread count. For example, if historical throughput statistics indicate that a higher thread count increased throughput, WebLogic increases the thread count. Similarly, if statistics indicate that fewer threads did not reduce throughput, WebLogic decreases the thread count. This new strategy makes it easier for administrators to allocate processing resources and manage performance, avoiding the effort and complexity involved in configuring, monitoring, and tuning custom executes queues.
- Create global Work Managers
- Create global constraints
- Create global request classes
- Monitor servers
- Configure health monitoring
- Create diagnostic system modules