Skip navigation.

Administration Console Online Help

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents Index

 


Execute Queue --> Configuration

Tasks     Related Topics     Attributes

Overview

Requests to a server instance are placed in an execute queue. Each request is assigned to a thread within the queue that performs the work.

By default, a new 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.HTTP—Available only on Administration Servers, this queue is reserved for communicating with the Administration Console; you cannot reconfigure it.

weblogic.admin.RMI—Both Administration Servers and Managed Servers have this queue; it is reserved for administrative traffic; you cannot reconfigure it.

Unless you configure additional execute queues, and assign applications to them, web applications and RMI objects use weblogic.kernel.default.

Use this page to configure a new, user-defined execute queue for use with applications on this server, or to edit an existing execute queue.

Tasks

Creating Execute Queues in WebLogic Server Performance and Tuning.

Tuning Execute Queues for Overflow Conditions in WebLogic Server Performance and Tuning.

Related Topics

Tuning the Default Execute Threads in WebLogic Server Performance and Tuning.

Using Execute Queues to Control Thread Usage in WebLogic Server Performance and Tuning.

Assigning Applications to Execute Queues in WebLogic Server Performance and Tuning.

Attributes

Table 324-1

Attribute Label

Description

Value Constraints

Name

The name of this execute queue.

MBean: weblogic.management.
configuration.
ExecuteQueueMBean

Attribute: Name


Queue Length

The maximum number of simultaneous requests that the server instance can hold in the queue.

Minimum: 256

Maximum: 1073741824

Default: 65536

Queue Length Threshold Percent

The percentage (from 1-99) of the Queue Length size that can be reached before the 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.

Minimum: 1

Maximum: 99

Default: 90

Thread Count

The number of threads assigned to this queue.

MBean: weblogic.management.
configuration.
ExecuteQueueMBean

Attribute: ThreadCount

Minimum: 0

Maximum: 65536

Default: 15

Threads Increase

The number of threads to be added to the queue when an overflow condition occurs. If you specify zero threads (the default), the server instance changes its health state to "warning" in response to an overflow condition in the thread, but it does not increase the thread count.

Minimum: 0

Maximum: 65536

Default: 0

Threads Maximum

The maximum number of threads that this queue can have; this value prevents WebLogic Server from creating an overly high thread count in the queue in response to continual overflow conditions.

MBean: weblogic.management.
configuration.
ExecuteQueueMBean

Attribute: ThreadsMaximum

Minimum: 1

Maximum: 65536

Default: 400

Thread Priority

The priority of the threads associated with this queue.

Minimum: 1

Maximum: 10

Default: 5

 

Skip navigation bar  Back to Top Previous Next