From 5833fe40996c75adcf1e116104ffe6169c4866e6 Mon Sep 17 00:00:00 2001
From: rhaggard <rhaggard@localhost>
Date: Fri, 01 Feb 2008 18:37:01 +0000
Subject: [PATCH] Uncommitting last changes to configuration .xml files, second try
---
opends/src/admin/defn/org/opends/server/admin/std/TraditionalWorkQueueConfiguration.xml | 40 +++++++---------------------------------
1 files changed, 7 insertions(+), 33 deletions(-)
diff --git a/opends/src/admin/defn/org/opends/server/admin/std/TraditionalWorkQueueConfiguration.xml b/opends/src/admin/defn/org/opends/server/admin/std/TraditionalWorkQueueConfiguration.xml
index d6ea5ad..2676413 100644
--- a/opends/src/admin/defn/org/opends/server/admin/std/TraditionalWorkQueueConfiguration.xml
+++ b/opends/src/admin/defn/org/opends/server/admin/std/TraditionalWorkQueueConfiguration.xml
@@ -37,24 +37,6 @@
watch a queue and pick up an operation to process whenever one
becomes available.
</adm:synopsis>
- <adm:description>
- The traditional work queue is named that because its implementation
- is similar to that used by the Sun Java System Directory Server.
- The traditional work queue is a FIFO queue serviced by a fixed
- number of worker threads. However, there are a couple of notable
- differences in its design: 1) The number of worker threads is fixed,
- but it can be changed on the fly and those changes take effect
- immediately. In the Sun Java System Directory Server, changes to the
- number of worker threads require a server restart to take effect.
- 2) The work queue in the Sun Java System Directory Server is
- unbounded. If all threads are busy processing existing operations
- and new requests arrive, they continue to accumulate in the work
- queue and the server appears to be frozen. In the OpenDS Directory
- Server, it is possible to place a size limit on the work queue.
- When this number of operations are in the queue, waiting to be
- picked up by threads, any new requests received are rejected with
- an error message.
- </adm:description>
<adm:profile name="ldap">
<ldap:object-class>
<ldap:name>ds-cfg-traditional-work-queue</ldap:name>
@@ -63,14 +45,11 @@
</adm:profile>
<adm:property name="num-worker-threads" mandatory="true">
<adm:synopsis>
- Specifies the number of worker threads to be used for processing
- operations placed in the queue. If the value is increased,
- the additional worker threads are created immediately. If the
- value is reduced, the appropriate number of threads are destroyed
- as operations complete processing.
+ The number of worker threads that should be used to process
+ operations placed into the queue.
</adm:synopsis>
<adm:syntax>
- <adm:integer lower-limit="1" upper-limit="2147483647" />
+ <adm:integer lower-limit="1" />
</adm:syntax>
<adm:profile name="ldap">
<ldap:attribute>
@@ -80,28 +59,23 @@
</adm:property>
<adm:property name="max-work-queue-capacity">
<adm:synopsis>
- Specifies the maximum number of queued operations that can be in the work
+ The maximum number of queued operations that can be in the work
queue at any given time.
</adm:synopsis>
<adm:description>
If the work queue is already full and additional requests are
- received by the server, the requests are rejected.
- A value of zero indicates that there is no limit to the size
- of the queue.
+ received by the server, they will be rejected.
</adm:description>
- <adm:requires-admin-action>
- <adm:server-restart />
- </adm:requires-admin-action>
<adm:default-behavior>
<adm:alias>
<adm:synopsis>
- The work queue does not impose any limit on the number of
+ The work queue will not impose any limit on the number of
operations that can be enqueued at any one time.
</adm:synopsis>
</adm:alias>
</adm:default-behavior>
<adm:syntax>
- <adm:integer lower-limit="0" upper-limit="2147483647"/>
+ <adm:integer lower-limit="0" />
</adm:syntax>
<adm:profile name="ldap">
<ldap:attribute>
--
Gitblit v1.10.0