| |
Execute Queue: Configuration
Configuration Options Related Topics
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.
Execute queues are provided for backward compatibility, but are turned off by default.
Each WebLogic Server instance is configured with a default execute queue, weblogic.kernel.default, that contains 15 threads. In addition, WebLogic Server provides two other pre-configured queues:
weblogic.admin.HTTPandweblogic.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 theweblogic.kernel.defaultexecute queue. When they are available, this page displays current runtime characteristics and statistics for the server's active execute queues.Configuration Options
Name Description Name The name of this execute queue.
MBean Attribute:
WebLogicMBean.NameChanges take effect after you redeploy the module or restart the server.
Queue Length The maximum number of simultaneous requests that this server can hold in the queue.
MBean Attribute:
ExecuteQueueMBean.QueueLengthMinimum value:
256Maximum value:
1073741824Changes take effect after you redeploy the module or restart the server.
Queue Length Threshold Percent The percentage of the Queue Length size that can be reached before this server indicates an overflow condition for the queue.
All actual queue length sizes below the threshold percentage are considered normal; sizes above the threshold percentage indicate an overflow. When an overflow condition is reached, WebLogic Server logs an error message and increases the number of threads in the queue by the value of the Threads Increase attribute to help reduce the workload.
MBean Attribute:
ExecuteQueueMBean.QueueLengthThresholdPercentMinimum value:
1Maximum value:
99Thread Count The number of threads assigned to this queue.
MBean Attribute:
ExecuteQueueMBean.ThreadCountMinimum value:
0Maximum value:
65536Changes take effect after you redeploy the module or restart the server.
Threads Increase Specifies the number of threads to increase the queue length when the queue length theshold is reached. This threshold is determined by the QueueLengthThresholdPercent value.
The following consideration applies to the dynamic nature of ThreadsMaximum and ThreadsIncrease attributes. If any of these attributes change during runtime, the changed value comes into effect when the next request is submitted to the execute queue and the scheduler decides to increase threads depending on the queue threshold conditions.
MBean Attribute:
ExecuteQueueMBean.ThreadsIncreaseMinimum value:
0Maximum value:
65536Threads Maximum The maximum number of threads that this queue is allowed to have; this value prevents WebLogic Server from creating an overly high thread count in the queue in response to continual overflow conditions.
A note about dynamic nature of ThreadsMaximum and ThreadsIncrease attributes. If any of these attributes change during runtime, the changed value comes into effect when the next request is submitted to the execute queue and the scheduler decides to increase threads depending on the queue threshold conditions. Imagine a scenario where the queue capacity has already reached the max threshold and the current thread count is already equal to ThreadsMaximum value. If more work is coming into the queue and the administrator wishes to increase the ThreadsMaximum a little to add a few more threads, he/she can do so by changing these attributes dynamically. Please note that the changed value is evaluated when the next request is submitted.
MBean Attribute:
ExecuteQueueMBean.ThreadsMaximumMinimum value:
1Maximum value:
65536Threads Minimum The minimum number of threads that WebLogic Server will maintain in the queue.
MBean Attribute:
ExecuteQueueMBean.ThreadsMinimumMinimum value:
0Maximum value:
65536Changes take effect after you redeploy the module or restart the server.
|