Stability and Performance - Oracle WebLogic Server 12c Advanced Administration - page 225

Tuning thread concurrency with the default
work manager
In production environments, keeping the computer resources such as memory, processes,
connections, and threads under control is essential to maintain a stable and predictable system.
For a WebLogic Administrator focused on stability, the top tuning recommendation for
WebLogic should be controlling the thread concurrency and resources usage.
In this recipe, the default work manager will be created to override the default settings with
a new maximum thread constraint named defaultMaxThreads and configured with 50,
targeting it to the cluster, PROD_Cluster .
Getting ready
The work manager will be created in the Administration Console.
How to do it...
Create the defaultMaxThreads maximum threads constraint and the default
work manager in the Administration Console by following the ensuing steps:
1. Access the Administration Console by pointing your web browser to
http://adminhost.domain.local:7001/console .
2. Click on the Lock & Edit button to start a new edit session.
3. Expand the Environment tree to the left and then click on Work Managers.
4. Click on the New button then select the Maximum Threads Constraint radio button.
Click on the Next button.
5. Enter defaultMaxThreads in the Name text field and 50 in the Count text field.
Click on the Next button.
6. Select the All servers in the cluster radio button from the PROD_Cluster option
and click on the Finish button.
7. Click on the New button again and select the Work Manager radio button. Click on
the Next button.