27 Aug, 2009

4 commits


26 Aug, 2009

6 commits


25 Aug, 2009

2 commits


24 Aug, 2009

3 commits


21 Aug, 2009

2 commits


20 Aug, 2009

1 commit


19 Aug, 2009

1 commit


18 Aug, 2009

2 commits


17 Aug, 2009

3 commits


14 Aug, 2009

3 commits


13 Aug, 2009

3 commits


12 Aug, 2009

2 commits

  • …execute the code of the method bootstrapClient once, however this is not ideal for some client codes.  Some methods, such as initializeConfiguration, require the DirectoryServer object to be 'clean' (freshly bootstrapped), this can only be achieved by executing all the code of bootstrapClient.
    
    The changes are actually just cosmetic, the logic in the code remains intact (simply the member isClientBootstrapped has been removed).
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5660 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • The code assumed that if the two registries were equal, then they were replicated.  This was wrong, if we disabled replication for one server, only the disabled server was unregistered from the ADS and this caused the problem (since the certificate of the previously unregistered server was not seeded).  The fix consists of two parts (even though just one of them would be enough to fix the issue, I think that having both will help the code to handle more scenarios):
    
    1. Check that if the registries are equal, they actually are replicated (in terms of configuration of the replication).
    2. Unregister ALL the servers from the ADS of the server where replication is being disabled if we have to unregister the server itself.  
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5654 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

11 Aug, 2009

3 commits


10 Aug, 2009

1 commit


07 Aug, 2009

1 commit

  • When checking dependencies during replay of operations on the consumer
    the replication go through the list of pending changes while holding the
    pending changes lock.
    When using large values for the window size, the list can be large
    and this can therefore cause large replication delay on the replica. 
    
    The solution is to limit the parsing to the list of changes that are older than the current change. 
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5636 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     

06 Aug, 2009

1 commit


05 Aug, 2009

1 commit

  • 4161 some mistranslations in german
    and
    4162 french: exception in setup
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5631 41b1ffd8-f28e-4786-ab96-9950f0a78031
    hajma
     

04 Aug, 2009

1 commit