public interface MinThreadsConstraintMBean extends DeploymentMBean
This MBean defines the minimum number of concurrent threads that should allocated to this constraint provided there are enough pending requests.
Multiple WorkManagers can share a common MinThreadsConstraint. MinThreadsConstraint perform their own bookkeeping and demand a thread when the constraint is not met and there are enough requests.
MinThreadsConstraint should be used to tell the WebLogic Server that a certain number of minimum threads are necessary to prevent server to server deadlocks. Although the server is self-tuning, specifying MinThreadsConstraint ensures that the server guarantees minimum threads to avoid the distributed deadlocks.
DEFAULT_ORDER, MAX_ORDER, MIN_ORDER
DEFAULT_EMPTY_BYTE_ARRAY
Modifier and Type | Method and Description |
---|---|
int |
getCount()
Minimum number of concurrent threads executing requests that share this
constraint.
|
void |
setCount(int count)
Min number of concurrent threads executing requests that share this
constraint.
|
addTarget, getDeploymentOrder, getTargets, removeTarget, setDeploymentOrder, setTargets
freezeCurrentValue, getId, getInheritedProperties, getName, getNotes, isDynamicallyCreated, isInherited, isSet, restoreDefaultValue, setComments, setDefaultedMBean, setName, setNotes, setPersistenceEnabled, unSet
getMBeanInfo, getObjectName, getParent, getType, isCachingDisabled, isRegistered, setParent
getAttribute, getAttributes, invoke, setAttribute, setAttributes
postDeregister, postRegister, preDeregister, preRegister
addNotificationListener, getNotificationInfo, removeNotificationListener
addPropertyChangeListener, createChildCopyIncludingObsolete, getParentBean, isEditable, removePropertyChangeListener
int getCount()
A count of 0 or -1 is treated as if the constraint is not present. This means that the constraint is ignored for these two values. A count > 0 can be dynamically changed to 0 to indicate that constraint enforcement is no longer needed.
void setCount(int count)
A count of 0 or -1 is treated as if the constraint is not present. This means that the constraint is ignored for these two values. A count > 0 can be dynamically changed to 0 to indicate that constraint enforcement is no longer needed.