From fc52704e1b5f3f221f433796a816e6f2f3f84a85 Mon Sep 17 00:00:00 2001
From: lfrost <lfrost@localhost>
Date: Fri, 07 Mar 2008 08:52:53 +0000
Subject: [PATCH] Fix for issue 2999. Reword the traditional work queue help to remove references to DSEE
---
opends/src/admin/defn/org/opends/server/admin/std/TraditionalWorkQueueConfiguration.xml | 21 ++++++---------------
1 files changed, 6 insertions(+), 15 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 b00f930..745c99f 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
@@ -38,22 +38,13 @@
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.
+ number of worker threads. This fixed number of threads can be
+ changed on the fly, with the change taking effect as soon as
+ it is made. You can limit the size of the work queue to a specified
+ number of operations. When this many operations are in the
+ queue, waiting to be picked up by threads, any new requests are
+ rejected with an error message.
</adm:description>
<adm:profile name="ldap">
<ldap:object-class>
--
Gitblit v1.10.0