Fixed another case where the too slow log message may arrive. This is relat...

mrossign

26.38.2009 ffc22dd5a175886f9d3661ad5122368ca8022934

Fixed another case where the too slow log message may arrive.
This is related to issue 4343 modifications.

 opends/src/server/org/opends/server/replication/server/ReplicationServer.java

@@ -1606,7 +1606,11 @@
    expectedMonitoringMsg =
      Collections.synchronizedList(new ArrayList<GlobalServerId>());

    for (ReplicationServerDomain domain : baseDNs.values())
    // Copy the list of domains as a new domain may arrive or disappear between
    // the initializeMonitorData and completeMonitorData calls
    List<ReplicationServerDomain> rsdList = new ArrayList(baseDNs.values());

    for (ReplicationServerDomain domain : rsdList)
    {
      domain.initializeMonitorData(expectedMonitoringMsg);
    }
@@ -1614,7 +1618,7 @@
    // Wait for responses
    waitMonitorDataResponses();

    for (ReplicationServerDomain domain : baseDNs.values())
    for (ReplicationServerDomain domain : rsdList)
    {
      domain.completeMonitorData();
    }

 opends/src/server/org/opends/server/replication/server/ReplicationServerDomain.java

@@ -2595,7 +2595,7 @@

      // Then initialize the max CN for the LS that produced something
      // - from our own local db state
      // - whatever they are directly or undirectly connected
      // - whatever they are directly or indirectly connected
      ServerState dbServerState = getDbServerState();
      wrkMonitorData.setRSState(replicationServer.getServerId(), dbServerState);
      Iterator<Integer> it = dbServerState.iterator();