org.forgerock / org.forgerock.opendj

22 Aug, 2007

5 commits

  • fded5520   issue 2119 : replication servers do not connect to each other when using setup ... Browse Code » 
    When using the setup to configure 2 servers in multimaster mode.
The setup first creates the configuration of the first server and start it
When the second setup is run to configure the second server, the setup updates
the configuration of the replication-server on the first server, however the code for handling this dynamic configuration was not yet written and this
information is not taken into account.

The replication servers are therefore not connected and the replication server
on the new host therefore does not get the updates.

These changes implement the dynamic configuration of replication servers so that
the same scenario works fine.

The only properties that is now not dynamically configurable is the
path of the changelog database.

A new test has been added for these changes.
I've also tested manually that this does fix the replication server problem
after configuration using the setup program. 

git-svn-id: https://svn.forgerock.org/opendj/trunk@2740 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • 2121df84   fix indentation misaligned in client auth tests ... Browse Code » 
    
git-svn-id: https://svn.forgerock.org/opendj/trunk@2739 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gary_williams
     
  • 6e32ec78   fix indentation misaligned in logging tests ... Browse Code » 
    
git-svn-id: https://svn.forgerock.org/opendj/trunk@2738 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gary_williams
     
  • 8084a202   issue 1804 : Ensure that conflicts are visible to administrators ... Browse Code » 
    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
     
  • caf1f215   Fix for 1602 : removing root entries of domain cause replay of many changes ... Browse Code » 
    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

19 commits