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/WorkQueueCfgDefn.properties |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/opends/src/admin/messages/WorkQueueCfgDefn.properties b/opends/src/admin/messages/WorkQueueCfgDefn.properties
index bff9ac4..f3b1af9 100644
--- a/opends/src/admin/messages/WorkQueueCfgDefn.properties
+++ b/opends/src/admin/messages/WorkQueueCfgDefn.properties
@@ -3,3 +3,6 @@
 synopsis=The Work Queue provides the configuration for the server work queue and is responsible for ensuring that requests received from clients are processed in a timely manner.
 description=Only a single work queue can be defined in the server. Whenever a connection handler receives a client request, it should place the request in the work queue to be processed appropriately.
 property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the 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.

--
Gitblit v1.10.0