diff options
| author | Andrea Gazzarini <agazzarini@apache.org> | 2009-02-14 10:49:38 +0000 |
|---|---|---|
| committer | Andrea Gazzarini <agazzarini@apache.org> | 2009-02-14 10:49:38 +0000 |
| commit | 9d7272bd07d103329494e293c31a26bb3a09476f (patch) | |
| tree | 0969aa81cafee09cdef869da4ff663bc3104dc7b /java/management/client/etc | |
| parent | 25ca58f5b141b88699aaf3e8680da5a12a85389b (diff) | |
| download | qpid-python-9d7272bd07d103329494e293c31a26bb3a09476f.tar.gz | |
QPID-1664 : QMan Asynchronous notification capability
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@744478 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'java/management/client/etc')
| -rw-r--r-- | java/management/client/etc/qman-config.xml | 31 |
1 files changed, 24 insertions, 7 deletions
diff --git a/java/management/client/etc/qman-config.xml b/java/management/client/etc/qman-config.xml index c1a5da9184..cdc840e967 100644 --- a/java/management/client/etc/qman-config.xml +++ b/java/management/client/etc/qman-config.xml @@ -18,13 +18,14 @@ - under the License. - --> -<!-- -Default configuration for QMan is empty; -that is, there's no broker configured at startup. -If you want to connect with a running broker when QMan starts up, -you can do that uncommenting and editing the template reported below. ---> <configuration> +
+<!--
+Default configuration for QMan has no broker settings;
+that is, there's no broker configured at startup.
+If you want to connect with a running broker when QMan starts up,
+you can do that uncommenting and editing the template reported below.
+-->
<!-- <brokers> <broker> <host>localhost</host> @@ -47,5 +48,21 @@ you can do that uncommenting and editing the template reported below. <max-wait-timeout>-1</max-wait-timeout> </broker> </brokers> - --> + -->
+ <!-- Internal worked manager configuration-->
+ <work-manager>
+ <!-- The size of the worker thread pool -->
+ <pool-capacity>5</pool-capacity>
+
+ <!-- Maximum size of the worker thread pool -->
+ <max-pool-capacity>15</max-pool-capacity>
+
+ <!--
+ when the current number of threads is greater than
+ the pool-capacity, this is the maximum time that excess threads
+ can be in an idle state (without any task assigned) before terminating.
+ The value is expressed is milliseconds.
+ -->
+ <keep-alive-time>5000</keep-alive-time>
+ </work-manager> </configuration> |