From 0181e868e5eb1e3896ed4b371947bed2ccb9aa50 Mon Sep 17 00:00:00 2001
From: neil_a_wilson <neil_a_wilson@localhost>
Date: Thu, 12 Oct 2006 15:08:00 +0000
Subject: [PATCH] Update the server code to eliminate the need for a 5-second delay when attempting to terminate a client connection from within an operation plugin. The issue arose when the attempt to terminate the connection tried to cancel the operation that initiated the disconnect, which made it necessary to wait for a 5-second timeout before continuing.

---
 opendj-sdk/opends/src/server/org/opends/server/api/ClientConnection.java |    6 +++++-
 1 files changed, 5 insertions(+), 1 deletions(-)

diff --git a/opendj-sdk/opends/src/server/org/opends/server/api/ClientConnection.java b/opendj-sdk/opends/src/server/org/opends/server/api/ClientConnection.java
index 7fec595..c813a3e 100644
--- a/opendj-sdk/opends/src/server/org/opends/server/api/ClientConnection.java
+++ b/opendj-sdk/opends/src/server/org/opends/server/api/ClientConnection.java
@@ -404,7 +404,11 @@
    * Closes the connection to the client, optionally sending it a
    * message indicating the reason for the closure.  Note that the
    * ability to send a notice of disconnection may not be available
-   * for all protocols or under all circumstances.
+   * for all protocols or under all circumstances.  Also note that
+   * when attempting to disconnect a client connection as a part of
+   * operation processing (e.g., within a plugin or other extension),
+   * the <CODE>disconnectClient</CODE> method within that operation
+   * should be called rather than invoking this method directly.
    *
    * @param  disconnectReason  The disconnect reason that provides the
    *                           generic cause for the disconnect.

--
Gitblit v1.10.0