Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# Monitoring Threads

Related Tasks Related Topics

When using Work Managers to prioritize thread execution, WebLogic Server uses a single thread pool, in which all types of work are executed. WebLogic Server prioritizes work based on rules you define, and run-time metrics, including the actual time it takes to execute a request and the rate at which requests are entering and leaving the pool.

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.

WebLogic Server provides another method for prioritizing and executing threads. This method is used for backward compatibility when using execute queues. In this method, different classes of work were executed in different queues, based on priority and ordering requirements, and to avoid deadlocks. In addition to the default execute queue, weblogic.kernel.default, there were pre-configured queues dedicated to internal administrative traffic, such as weblogic.admin.HTTP and weblogic.admin.RMI.

Related Tasks

- Create a Global Work Manager
- Create a Global Constraint
- Create a Global Request Class
- Monitor servers
- Configure health monitoring
- Create diagnostic system modules

Related Topics

- Using Work Managers to Optimize Scheduled Work
- Avoiding and Recovering From Server Failure
- Avoiding and Managing Overload
- Understanding Server Life Cycle
- Managing Server and Server Life Cycle