Thread Service – Configuration
Command-line (-D) Properties
- org.cougaar.thread.trivial
- Set this to “true” to use the extremely simple Thread Service implementation (with no Schedulers, control, or listener callbacks). Later this will be handled via Component Descriptions.
Component Parameters
- BestEffortAbsCapacity
- Set this to an integer to specify the maximum number of threads that can ever run in the
BEST_EFFORT_LANE. This only has relevance for the Node-level Thread Service. The default value is 300.
- WillBlockAbsCapacity
- Set this to an integer to specify the maximum number of threads that can ever run in the
WILL_BLOCK_LANE. This only has relevance for the Node-level Thread Service. The default value is 30.
- CpuIntenseAbsCapacity
- Set this to an integer to specify the maximum number of threads that can ever run in the
CPU_INTENSE_LANE. This only has relevance for the Node-level Thread Service. The default value is 2.
- WellBehavedAbsCapacity
- Set this to an integer to specify the maximum number of threads that can ever run in the
WELL_BEHAVED_LANE. This only has relevance for the Node-level Thread Service. The default value is 2.
Servlets
- org.cougaar.core.thread.TopPlugin
- Dumps the currently running or queued
Schedulables. It does not depend on the Metrics Service. This should be loaded into the NodeAgent.
- org.cougaar.core.thread.AgentSensorPlugin
- Publishes per-agent load average data into the Metrics Service. This should be loaded into the NodeAgent.
- org.cougaar.core.thread.ThreadWellBehavedPlugin
- Loading this plugin into an Agent causes that Agent to use the WELL_BEHAVED_LANE as its default. The plugin also accepts a parameter “defaultLane” to set some other initial default. For now the parameter value should be given directly as an integer, not symbolically.
