| |
Servers: Monitoring: Threads
Column Display Related Tasks Related Topics
This page provides information on the thread activity for the current server.
The first table provides general information about the status of the thread pool. The second table provides information on individual threads.
Note: The user ID displayed for individual threads is the user ID executing the thread during the current stage of the request. This table may display different user IDs during the lifecycle of the thread.
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.
Column Display
You can show fewer or additional data points on this page by expanding Customize this table and modifying the Column Display list. Each data point displays in its own table column.
The following table lists all of the data points that you can display in columns on this page.
Name Description Active Execute Threads The number of active execute threads in the pool, computed by using the following formula: ThreadPoolRuntimeMBean.ExecuteThreadTotalCount - (ThreadPoolRuntimeMBean.StandbyThreadCount + ThreadPoolRuntimeMBean.ExecuteThreadIdleCount + ThreadPoolRuntimeMBean.StuckThreadCount)
Total Execute Threads The total number of threads in the pool.
MBean Attribute:
ThreadPoolRuntimeMBean.ExecuteThreadTotalCountIdle Execute Threads The number of idle threads in the pool. This count does not include standby threads and stuck threads. The count indicates threads that are ready to pick up new work when it arrives
MBean Attribute:
ThreadPoolRuntimeMBean.ExecuteThreadIdleCountQueue Length The number of pending requests in the priority queue. This is the total of internal system requests and user requests.
MBean Attribute:
ThreadPoolRuntimeMBean.QueueLengthPending Requests The number of pending user requests in the priority queue. The priority queue contains requests from internal subsystems and users. This is just the count of all user requests.
MBean Attribute:
ThreadPoolRuntimeMBean.PendingUserRequestCountShared Capacity For Work Managers Maximum amount of requests that can be accepted in the priority queue. Note that a request with higher priority will be accepted in place of a lower priority request already in the queue even after the threshold is reached. The lower priority request is kept waiting in the queue till all high priority requests are executed. Also note that further enqueues of the low priority requests are rejected right away.
MBean Attribute:
ThreadPoolRuntimeMBean.SharedCapacityForWorkManagersCompleted Requests The number of completed requests in the priority queue.
MBean Attribute:
ThreadPoolRuntimeMBean.CompletedRequestCountOverload Rejected Requests Number of requests rejected due to configured Shared Capacity for work managers have been reached.
MBean Attribute:
ThreadPoolRuntimeMBean.OverloadRejectedRequestsCountHogging Threads The threads that are being held by a request right now. These threads will either be declared as stuck after the configured timeout or will return to the pool before that. The self-tuning mechanism will backfill if necessary.
MBean Attribute:
ThreadPoolRuntimeMBean.HoggingThreadCountStandby Threads The number of threads in the standby pool. Threads that are not needed to handle the present work load are designated as standby and added to the standby pool. These threads are activated when more threads are needed.
MBean Attribute:
ThreadPoolRuntimeMBean.StandbyThreadCountStuck Threads Number of stuck threads in the thread pool.
MBean Attribute:
ThreadPoolRuntimeMBean.StuckThreadCountThroughput The mean number of requests completed per second.
MBean Attribute:
ThreadPoolRuntimeMBean.ThroughputMin Threads Constraints Pending Number of requests that should be executed now to satisfy the min threads requirement.
MBean Attribute:
ThreadPoolRuntimeMBean.MinThreadsConstraintsPendingMin Threads Constraints Completed Number of requests with min threads constraint picked up out of order for execution immediately since their min threads requirement was not met. This does not include the case where threads are idle during schedule.
MBean Attribute:
ThreadPoolRuntimeMBean.MinThreadsConstraintsCompletedSuspended Indicates if the RequestManager is suspended. A suspended manager will not dequeue work and dispatch threads till it is resumed.
MBean Attribute:
ThreadPoolRuntimeMBean.SuspendedHealth The health state of this pool.
MBean Attribute:
ThreadPoolRuntimeMBean.HealthStateColumn Display
You can show fewer or additional data points on this page by expanding Customize this table and modifying the Column Display list. Each data point displays in its own table column.
The following table lists all of the data points that you can display in columns on this page.
Name Description Name The name of the execute thread.
Total Requests The number of requests which have been processed by this queue.
Current Request The request this thread is currently processing.
Transaction The transaction on behalf of which the execute thread is currently working.
User The user on behalf of which the execute thread is currently working.
Idle True if the execute thread has no work assigned to it.
Stuck True if the execute thread is stuck working on a request for more than the configured stuck thread maximum time.
Hogger True if the execute thread is being hogged by a request for much more than the normal execution time, as automatically observed by the scheduler.
Standby True if the execute thread is not a part of the active thread pool.
Work Manager The name of the current work manager.
Application The name only, without the version number, of the application using the context class loader of the thread.
Module The module using the context class loader of the thread.
|