From ff3d9f4d66359580bd48d255a86a7e2099d7ed4f Mon Sep 17 00:00:00 2001
From: ludovicp <ludovicp@localhost>
Date: Fri, 30 Jul 2010 15:32:42 +0000
Subject: [PATCH] Ldaptools should not timeout by default when processing operations (some delete or searches may take a long time, especially subtree deletes and persistent searches).
---
opends/src/server/org/opends/server/tools/LDAPDelete.java | 4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/opends/src/server/org/opends/server/tools/LDAPDelete.java b/opends/src/server/org/opends/server/tools/LDAPDelete.java
index 1c5c127..c05a482 100644
--- a/opends/src/server/org/opends/server/tools/LDAPDelete.java
+++ b/opends/src/server/org/opends/server/tools/LDAPDelete.java
@@ -25,7 +25,6 @@
* Copyright 2006-2010 Sun Microsystems, Inc.
*/
package org.opends.server.tools;
-import org.opends.admin.ads.util.ConnectionUtils;
import org.opends.messages.Message;
import java.io.BufferedReader;
@@ -540,11 +539,10 @@
version.setPropertyName(OPTION_LONG_PROTOCOL_VERSION);
argParser.addArgument(version);
- int defaultTimeout = ConnectionUtils.getDefaultLDAPTimeout();
connectTimeout = new IntegerArgument(OPTION_LONG_CONNECT_TIMEOUT,
null, OPTION_LONG_CONNECT_TIMEOUT,
false, false, true, INFO_TIMEOUT_PLACEHOLDER.get(),
- defaultTimeout, null,
+ 0, null,
true, 0, false, Integer.MAX_VALUE,
INFO_DESCRIPTION_CONNECTION_TIMEOUT.get());
connectTimeout.setPropertyName(OPTION_LONG_CONNECT_TIMEOUT);
--
Gitblit v1.10.0