16 Sep, 2009

1 commit


15 Sep, 2009

3 commits


14 Sep, 2009

4 commits

  • git-svn-id: https://svn.forgerock.org/opendj/trunk@5829 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jpikus
     
  • * Update tools and properties files to use the DynamicConstants class definitions :
       Product Name, Short Name, Version etc ...
         * setup, uninstall, control-panel, upgrade.
    * Update the ID for ST registration for the coming milestone OpenDS 2.2
    * Update the welcome screen to use the DynamicConstants class definitions .
      In particular update the documentation pointer and description.
    * Replace the link to the QuickReference Guide by the Administration Guide
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5828 41b1ffd8-f28e-4786-ab96-9950f0a78031
    fguigues
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@5827 41b1ffd8-f28e-4786-ab96-9950f0a78031
    pgamba
     
  • When dsreplication enable runs it create the replication servers configuration
    then the replication domain configuration
    then attempt to perform an initialization
    
    if this attempt is made too quickly following the creation of the configuration it
    can happen that the replication servers are not connected when the initialization 
    is started and the routing tables of the replications servers not accurate.
    
    This fix synchronize the creation of the replication server domain with the 
    replication server thread in charge of connecting the replication servers 
    together so that this problem can't occur anymore.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5826 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     

12 Sep, 2009

2 commits


10 Sep, 2009

2 commits


09 Sep, 2009

3 commits


08 Sep, 2009

4 commits


07 Sep, 2009

4 commits

  • git-svn-id: https://svn.forgerock.org/opendj/trunk@5785 41b1ffd8-f28e-4786-ab96-9950f0a78031
    pgamba
     
  • Description
    
    Example:
      Using 1 suffix, 2 DSes on which write operations are done when replication is enabled.
      After a given time (24 h by default config), the replication db is trimed.
      Searching the ECL, returns then the latest change done for each (DS, suffix).
      This result is not correct :
        - because the db is supposed to be trimmed
        - because it does not respect time consistency, since it  contains some old changes (for example from DS1) while it does not contain some more recent changes (for example 
    from DS2).
    
    Roughly, this happens because the ECL relies on the "logical" replication changelog db, and because of the triming policy of the changelog db. 
    With more details, the replication db is made of one db instance by (DS, suffix) tuple. Trimming the "changelog db" consists in trimming each db instance, and for each 
    instance to always leave at least the latest change (for some reason purely replication oriented).
    
    The fix of the ECL consists in :
    - at the beginning of the ECL search processing, getting the latest trim date from each replication server domain (stored when trim is done)
    - when each change is processed, to skip it when it is older than the latest trim date of the domain.
    
    From the above example:
      Now the ECL is empty after the changelog db trimming.
    
    Diff
    Code and new unit test
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5784 41b1ffd8-f28e-4786-ab96-9950f0a78031
    pgamba
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5783 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@5778 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     

04 Sep, 2009

2 commits


03 Sep, 2009

4 commits


02 Sep, 2009

1 commit


01 Sep, 2009

3 commits


31 Aug, 2009

2 commits


28 Aug, 2009

1 commit


27 Aug, 2009

4 commits