From 332dcba0b9acaab991911fdd8aed6c3e2615e088 Mon Sep 17 00:00:00 2001
From: matthew_swift <matthew_swift@localhost>
Date: Fri, 17 Sep 2010 22:46:18 +0000
Subject: [PATCH] Refactor configuration of maximum persistent search resource limits

---
 opends/src/admin/messages/WorkQueueCfgDefn.properties |    3 ---
 1 files changed, 0 insertions(+), 3 deletions(-)

diff --git a/opends/src/admin/messages/WorkQueueCfgDefn.properties b/opends/src/admin/messages/WorkQueueCfgDefn.properties
index f3b1af9..bff9ac4 100644
--- a/opends/src/admin/messages/WorkQueueCfgDefn.properties
+++ b/opends/src/admin/messages/WorkQueueCfgDefn.properties
@@ -3,6 +3,3 @@
 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