From 3548261f7448ab41a3a9211e75b2ef554b4d20c6 Mon Sep 17 00:00:00 2001
From: pgamba <pgamba@localhost>
Date: Thu, 14 Feb 2008 09:02:33 +0000
Subject: [PATCH] No Issue associated. A replication server RS registers under cn=monitor one entry for each peer RS, and one entry for each LS remotely connected to the peer RS (Undirect LDAP server entry). When the remote RS has new LS connecting to it, or LS disconnecting from it, it notifies the other RSes .. that's fine. But when the connection between our RS and the peer RS itself is broken, some entities remains under cn=monitor while they should be removed.
---
opends/src/server/org/opends/server/replication/server/ServerHandler.java | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/opends/src/server/org/opends/server/replication/server/ServerHandler.java b/opends/src/server/org/opends/server/replication/server/ServerHandler.java
index 2d8cf9c..53c038c 100644
--- a/opends/src/server/org/opends/server/replication/server/ServerHandler.java
+++ b/opends/src/server/org/opends/server/replication/server/ServerHandler.java
@@ -1280,6 +1280,13 @@
{
active = false;
+ // Stop the remote LSHandler
+ for (LightweightServerHandler lsh : connectedServers.values())
+ {
+ lsh.stopHandler();
+ }
+ connectedServers.clear();
+
try
{
session.close();
--
Gitblit v1.10.0