03 Aug, 2011

1 commit


02 Aug, 2011

2 commits


29 Jul, 2011

2 commits


28 Jul, 2011

2 commits


27 Jul, 2011

1 commit


25 Jul, 2011

1 commit


21 Jul, 2011

1 commit


20 Jul, 2011

4 commits


18 Jul, 2011

2 commits


13 Jul, 2011

2 commits


05 Jul, 2011

2 commits


04 Jul, 2011

1 commit

  • The conflict resolution code didn't consider the case where a single modify operation could contain multiple modifications on an attribute, especially a replace after adds or delete. All changeNumbers would then be equals. Replace always wins over all precedent operations on the attribute, as Modifications are ordered (Sequence of).
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@7090 41b1ffd8-f28e-4786-ab96-9950f0a78031
    ludo
     

29 Jun, 2011

2 commits


28 Jun, 2011

4 commits


27 Jun, 2011

1 commit


24 Jun, 2011

2 commits


23 Jun, 2011

1 commit

  • Processing of the string based cookie was not handling errors consistently, as code was duplicated between the constructor and another parsing method. 
    The fix required some minor refactoring.
    All nightlytests have been successfully passing on my development machine.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@7052 41b1ffd8-f28e-4786-ab96-9950f0a78031
    ludo
     

22 Jun, 2011

1 commit

  • The value part of control specification is optional. And therefore there should be no : to finish the specification.
    Now if the specification ends with :, then it's the same as no value.
    Test added with the ManageDSAIt control.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@7049 41b1ffd8-f28e-4786-ab96-9950f0a78031
    ludo
     

20 Jun, 2011

1 commit


16 Jun, 2011

2 commits


15 Jun, 2011

2 commits


10 Jun, 2011

2 commits


09 Jun, 2011

1 commit

  • …ns servers which have been subjected to different purging policies.
    
    The issue of ECL change number inconsistency across servers is not tied to purging policies but to the fact that the CN is based on a lazy built index. As a result, the last change number in the index database depends on when Searches are done against the server and not what are really the changes available. The lastChangeNumber virtual attribute uses the index last CN and adds the changes received and eligible.
    
    The changes here are of fixing the following :
    After purging of the DraftCNDB, the next value will be incremented from last known value. As a result, changeNumbers are always increasing. Purging the DraftCNDB is now stopping at the first index that still points to a valid change in the changelog. The counter of changes has been fixed to take into account the fact that the changelog keeps at least one change older than the trim age in order to preserve the validity of the Cookie for at least "purge delay".
    Also contains some optimization of the DraftCNDBCursor to avoid reading the entries pointed by the cursor several times.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6994 41b1ffd8-f28e-4786-ab96-9950f0a78031
    ludo