22 Aug, 2007

3 commits

  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2738 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gary_williams
     
  • The replication monitoring information already provides the
    attribute unresolved-naming-conflicts that counts the number of conflicts
    that was not automatically resolved since last startup.
    
    The conflicting entries are also marked with the ds-sync-confict attribute
    so that administrators can look for these entries 
    using filter ds-sync-confict=*
    
    This code add the generation of an administrative alert when a conflict is
    detected so that administrators can be made aware of the problem.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2737 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • Before this fix, If one remove the root entry of a replication domain,
    then stop the server The PersistentServerState is lost.
    Therefore when later restarting the server all the changes from
    the replication server are replayed on the database.
    
    To avoid this the fix is simply to store the PersistentServerState to the configuration entry when the root entry does not exist.
    
    I have not developed a unit test for this scenario because I believe that it is not possible to restart the server during the unit test.
    I have done manual tests to check that the PersistentServerState
    is correctly saved and reread. 
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2736 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     

21 Aug, 2007

16 commits


20 Aug, 2007

21 commits