From 08f9243b55eb5f0f8030eebe976a0d85ffbd44c2 Mon Sep 17 00:00:00 2001 From: ludovicp <ludovicp@localhost> Date: Fri, 30 Jul 2010 15:11:25 +0000 Subject: [PATCH] Implements a configurable limit in the number of persistent searches a server can handle. --- opends/src/admin/messages/TraditionalWorkQueueCfgDefn.properties | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/opends/src/admin/messages/TraditionalWorkQueueCfgDefn.properties b/opends/src/admin/messages/TraditionalWorkQueueCfgDefn.properties index 4788e5f..5794795 100644 --- a/opends/src/admin/messages/TraditionalWorkQueueCfgDefn.properties +++ b/opends/src/admin/messages/TraditionalWorkQueueCfgDefn.properties @@ -3,6 +3,9 @@ synopsis=The Traditional Work Queue is a type of work queue that uses a number of worker threads that watch a queue and pick up an operation to process whenever one becomes available. description=The traditional work queue is a FIFO queue serviced by a fixed 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. property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Traditional Work Queue implementation. +property.max-psearches.synopsis=Defines the maximum number of concurrent persistent searches that can be performed on Directory Server +property.max-psearches.description=The persistent search mechanism provides an active channel through which entries that change, and information about the changes that occur, can be communicated. Because each persistent search operation uses one thread, limiting the number of simultaneous persistent searches prevents certain kinds of denial of service attacks. A value of 0 indicates that there is no limit on the persistent searches. +property.max-psearches.default-behavior.alias.synopsis=Let the server decide. property.max-work-queue-capacity.synopsis=Specifies the maximum number of queued operations that can be in the work queue at any given time. property.max-work-queue-capacity.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. property.max-work-queue-capacity.default-behavior.alias.synopsis=The work queue does not impose any limit on the number of operations that can be enqueued at any one time. -- Gitblit v1.10.0