Work Manager
Configuration Options Related Tasks Related Topics
A Work Manager defines a set of request classes and thread constraints that manage work performed by WebLogic Server instances. This page displays the Work Managers, request classes and thread constraints defined for this domain.
Work Managers are defined at the domain and partition level. You can also define application-level and module-level Work Managers.
WebLogic Server lets you configure how your application prioritizes the execution of its work based on rules you define and by monitoring actual runtime performance. You define the rules and constraints for your application by defining a Work Manager and applying it either globally to a WebLogic Server domain, to a specific domain partition, or to a specific application component.
Partition Work Managers define a set of thread constraints that manage work in partitions only. They do not apply to the domain.
Thread constraints define the maximum number of threads to allocate for requests, the minimum number of threads to use for resolving deadlocks, and the total number of requests that can be queued or running before WebLogic Server begins rejecting requests.
Java EE applications, Web application modules, EJBs, and RMI applications can specify a named Work Manager to use for managing their work requests.
Configuration Options
Name Description Partition Fair Share A desired percentage of thread usage by a partition compared to the thread usage by all partitions. It is recommended that the sum of this value for all the partitions running in a WLS domain add up to 100, but it is not strictly enforced. When they do not add up to 100, WLS assigns thread-usage times to different partitions based on their relative values. This attribute is for use in the global domain only. Use the PartitionWorkManager MBean for specifying partition fair share values for partitions.
MBean Attribute:
SelfTuningMBean.PartitionFairShare
Minimum value:
1
Maximum value:
99