OTN Home > Oracle WebLogic Server 12.2.1.4.0 Documentation > Administration Console Online Help > Configure domain partition concurrent constraints

Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Configure domain partition concurrent constraints


Note: WebLogic Server Multitenant domain partitions are deprecated in WebLogic Server 12.2.1.4.0. The related Console and help pages will be removed in the next release.

Long-running tasks submitted to the managed executor service, the managed scheduled executor service, or the managed thread factory method need to create new threads that will not be managed as a part of WebLogic Server's self-tuning thread pool. Because an excessive number of running threads can have a negative affect on server performance and stability, you can specify the maximum number of running threads that are created by the concurrency utilities API in the partition.

For information about configuring and using the concurrent managed objects (CMOs) in Oracle WebLogic Server, see "Configuring Concurrent Managed Objects" in Administering Server Environments for Oracle WebLogic Server.

To configure concurrent contraints in the current partiion:

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
  2. IIn the Domain Structure tree, select Domain Partitions.

    The Domain Partitions table displays all of the partitions defined in the domain scope.

  3. Select the partition in which you want to configure the concurrent constraints.
  4. Select Configuration > General > Concurrency.
    1. In Max Concurrent New Threads, enter the maximum number of concurrent new threads that can be created by all of the Managed Thread Factories in this partition scope.
    2. In Max Concurrent Long Requests, enter the maximum number of concurrent long-running requests that can be submitted to all of the Managed Executor Services or Managed Scheduled Executor Services in this partition scope.
  5. Click Save.
  6. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).

Back to Top