From 2c7e382da347e11820463fcf977d885c2f40d764 Mon Sep 17 00:00:00 2001
From: Valery Kharseko <vharseko@3a-systems.ru>
Date: Thu, 10 Sep 2026 08:50:34 +0000
Subject: [PATCH] [#917] Wait for every peer replication server to forward the ReplicaOfflineMsg (#947)
---
opendj-server-legacy/src/main/java/org/opends/server/replication/server/ReplicationServer.java | 9 +++++++++
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/opendj-server-legacy/src/main/java/org/opends/server/replication/server/ReplicationServer.java b/opendj-server-legacy/src/main/java/org/opends/server/replication/server/ReplicationServer.java
index ef1ba8b..29a5572 100644
--- a/opendj-server-legacy/src/main/java/org/opends/server/replication/server/ReplicationServer.java
+++ b/opendj-server-legacy/src/main/java/org/opends/server/replication/server/ReplicationServer.java
@@ -1226,6 +1226,15 @@
* Waits for the ReplicaOfflineMsg of every domain which has a replication server to forward it
* to. With no such server connected there is nobody to forward the message to, and waiting
* would only delay the shutdown by the whole grace period.
+ * <p>
+ * The recipients DSRSShutdownSync records when the message is queued are the sharper source of
+ * truth and cover the domains this test lets through - a peer which connected after the
+ * message was queued owes nothing, and is not waited for. What this test still covers is the
+ * announcement which was never queued here at all, and for which no recipient can therefore be
+ * recorded: the message of a replica which picked a remote replication server, or the
+ * announcement of issue #918 recorded after its message was relayed. Those wait out the whole
+ * grace period on the first forward, and on a server with no peer connected nothing would ever
+ * report one.
*/
private void awaitReplicaOfflineMsgsForwarded()
{
--
Gitblit v1.10.0