The Partition Work Managers table displays the defined Partition Work Managers.

1. In the Shared Capacity field, enter a number between 1 and 100.

   The partition-shared capacity for Work Managers limit the number of work requests from a partition. This limit includes work requests that are either running or queued waiting for an available thread. When the limit is exceeded, WLS will start rejecting certain requests submitted from the partition.

   The value is expressed as a percentage of the capacity of the entire WLS Server as configured in the "Shared Capacity For Work Managers" option that throttles the number of requests in the entire WLS Server instance. The partition-shared capacity for Work Managers must be a value between 1 and 100 percent.

2. In the Fair Share field, enter a number between 1 and 99.

   The fair share value is a desired percentage of thread usage of that partition compared to the thread usage of all partitions. The value must be a number between 1 and 99. Oracle recommends that the sum of this value for all partitions running in a WLS domain add up to 100. By default, a partition has a fair share value of 50.

3. (Optional) Specify a Minimum Threads Constraint value.

   A minimum threads constraint guarantees a number of threads the server will allocate to a Work Manager to avoid deadlocks. This could result in a Work Manager receiving more thread use time than its configured fair share, and thus, a partition getting more thread usage time than it should compared to other partitions in the same WLS server instance.

   You can optionally provide a limit on the minimum threads constraint value for each partition configured in the WLS domain. If configured, this imposes an upper limit on the minimum threads constraint values configured in a partition. If the sum of the configured values of all minimum threads constraints in a partition exceeds this configured value, a warning message will be logged and WLS will reduce the number of threads the thread pool will allocate for the constraints.

   By default, no minimum threads constraint limit is set on a partition.

4. (Optional) Specify a Maximum Threads Constraint value, the maximum number of threads in the self-tuning thread pool that are concurrently working on requests from a partition.

   A maximum threads constraint can be useful to prevent a partition from using more than its fair share of thread resources, especially in abnormal situations such as when threads are blocked on I/O, waiting for responses from a remote server that is not responding. Setting a maximum threads constraint in such a scenario would help ensure that some threads would be available for processing requests from other partitions in the WLS instance.