09 Jun, 2011

1 commit


08 Jun, 2011

2 commits


07 Jun, 2011

1 commit


06 Jun, 2011

3 commits


01 Jun, 2011

3 commits


31 May, 2011

3 commits


30 May, 2011

6 commits

  • …hanges with updates and purging.
    More specifically these changes are resolving the following issues :
    OPENDJ-57 - ECL: lastChangeNumber and firstChangeNumber reset to zero when the changelog is purged to empty
    OPENDJ-172 - External ChangeLog Cookie varies when searching with an empty cookie. Cookie should be reproducible.
    OPENDJ-173 - External ChangeLog cookies content is altered by Change purging and prevents from continuing search with a previous returned cookie.
    
    The changes are multiples and interdependant, hence a single commit.
    But : 
    - The DraftCNDB is now purged but always keep the last record. The firstKey value is updated accordingly.
    - The ReplicationDB is purged but always keep the last record before the trimdate.
    - If no cookie is specified, the initial cookie is computed from the ReplicationDomain StartState, but keeping only change numbers older than the trimdate. 
    - Fix a possible issue when searching a ChangeNumber, and a Count record is found, the changeNumber value was not correct.
    
    These changes mostly revert revision  6406 which meant to fix the same issue (cookies would become obsolete and a search using them returns an Unwilling To Perform), but only managed to hide the root cause of the issue.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6943 41b1ffd8-f28e-4786-ab96-9950f0a78031
    ludo
     
  • Finally, the lastExternalChangelogCookie attribute should be consistent with the ChangeLogCookie operational attribute. 
    Let's make them both DirectoryString.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6942 41b1ffd8-f28e-4786-ab96-9950f0a78031
    ludo
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@6941 41b1ffd8-f28e-4786-ab96-9950f0a78031
    ludo
     
  • …astExternalChangelogCookie.
    firstChangeNumber and lastChangeNumber are now Integer, single valued.
    The lastExternalChangelogCookie is an opaque set of bytes. I agree it looks like a string, but it would be better handled as opaque, thus an OCTET STRING. I'm marking it SINGLE-VALUE though.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6940 41b1ffd8-f28e-4786-ab96-9950f0a78031
    ludo
     
  • No brainer : If there's no value, create an empty MultiDomainServerState. The server already knows how to deal with them. 
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6938 41b1ffd8-f28e-4786-ab96-9950f0a78031
    ludo
     
  • Fix now check if the control is present in the search and returns it only if so.
    Tests have been added in unit-tests to verify this.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6936 41b1ffd8-f28e-4786-ab96-9950f0a78031
    ludo
     

19 May, 2011

3 commits


17 May, 2011

1 commit


16 May, 2011

4 commits


12 May, 2011

1 commit


10 May, 2011

5 commits


21 Apr, 2011

1 commit


20 Apr, 2011

1 commit


19 Apr, 2011

3 commits


18 Apr, 2011

2 commits