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

cmo.setCapacity(getMBean('/SelfTuning/PROD_DOMAIN/Capacities/
myWebServiceCapacityConstraint'))
cmo.setIgnoreStuckThreads(true)
activate()
exit()
See also
F Tuning thread concurrency with the default work manager
F Limiting the JMS Queue consumers
Limiting the JMS Queue consumers
By default, an MDB (message driven bean) uses up to 16 threads per WebLogic Server
instance to consume a JMS Queue destination.
In this recipe, an MDB QueueMDB from the hypothetical JMSApp application will be configured
to use only one thread to consume the JMS Queue. This will be done by creating a new work
manager jmsAppWM with a maximum thread constraint jmsAppMaxThreads with the value 1
and update the MDB descriptor to associate the new work manager.
Getting ready
The work manager will be defined in the Administration Console. The MDB descriptor must
also update a descriptor in order to be associated with the new work manager.
How to do it...
First, create the jmsAppMaxThreads maximum threads constraint and the jmsAppWM work
manager in the Administration Console:
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 and then select the Maximum Threads Constraint radio
button. Click on the Next button.