From cf6a30a62ca4cef27254d68e27f96431188bb4a3 Mon Sep 17 00:00:00 2001 From: ludovicp <ludovicp@localhost> Date: Wed, 18 Aug 2010 15:41:44 +0000 Subject: [PATCH] Update to messages and localized messages. --- opends/src/admin/messages/ParallelWorkQueueCfgDefn.properties | 19 ++++++++----------- 1 files changed, 8 insertions(+), 11 deletions(-) diff --git a/opends/src/admin/messages/ParallelWorkQueueCfgDefn.properties b/opends/src/admin/messages/ParallelWorkQueueCfgDefn.properties index 42223e4..d048f2c 100644 --- a/opends/src/admin/messages/ParallelWorkQueueCfgDefn.properties +++ b/opends/src/admin/messages/ParallelWorkQueueCfgDefn.properties @@ -1,11 +1,8 @@ -user-friendly-name=Parallel Work Queue -user-friendly-plural-name=Parallel Work Queues -synopsis=The Parallel 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 parallel 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. This work queue implementation is unbound ie it does not block after reaching certain queue size and as such should only be used on a very well tuned server configuration to avoid potential out of memory errors. -property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Parallel 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.num-worker-threads.synopsis=Specifies the number of worker threads to be used for processing operations placed in the queue. -property.num-worker-threads.description=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. -property.num-worker-threads.default-behavior.alias.synopsis=Let the server decide. +user-friendly-name=Parallel Work Queue +user-friendly-plural-name=Parallel Work Queues +synopsis=The Parallel 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 parallel 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. This work queue implementation is unbound ie it does not block after reaching certain queue size and as such should only be used on a very well tuned server configuration to avoid potential out of memory errors. +property.java-class.synopsis=Specifies the fully-qualified name of the Java class that provides the Parallel Work Queue implementation. +property.num-worker-threads.synopsis=Specifies the number of worker threads to be used for processing operations placed in the queue. +property.num-worker-threads.description=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. +property.num-worker-threads.default-behavior.alias.synopsis=Let the server decide. -- Gitblit v1.10.0