20 Aug, 2007

16 commits

  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2701 41b1ffd8-f28e-4786-ab96-9950f0a78031
    smaguin
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2700 41b1ffd8-f28e-4786-ab96-9950f0a78031
    smaguin
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2699 41b1ffd8-f28e-4786-ab96-9950f0a78031
    smaguin
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@2698 41b1ffd8-f28e-4786-ab96-9950f0a78031
    kenneth_suter
     
  • method, if any, in related entry cache implementation.
    - use ServerConstants.EOL where appropriate.
    - enable entry cache unit tests again [IllegalMonitorStateException should be 
      resolved in r2688/FileSystemEntryCache.java].
     
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2697 41b1ffd8-f28e-4786-ab96-9950f0a78031
    abobrov
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2696 41b1ffd8-f28e-4786-ab96-9950f0a78031
    smaguin
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2695 41b1ffd8-f28e-4786-ab96-9950f0a78031
    smaguin
     
  • - make toVerboseString method private in implementation classes.
    - make toVerboseString use StringBuilder instead of string concat.
    - make toVerboseString use ServerConstants.EOL where required.
     
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2694 41b1ffd8-f28e-4786-ab96-9950f0a78031
    abobrov
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2693 41b1ffd8-f28e-4786-ab96-9950f0a78031
    smaguin
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2692 41b1ffd8-f28e-4786-ab96-9950f0a78031
    smaguin
     
  • The test was not working as designed.
    The goal was to test dependecies of ADD/DEL/ADD sequence but the test 
    was trying to create children of entries already deleted, therefore 
    mixing naming conflict resolution with dependency resolution.
    
    The test now create and delete independent entries and should work
    better, I have therefore re-enabled it.
    
    No modification was done to the server itself.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2691 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2690 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gary_williams
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2689 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gary_williams
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2688 41b1ffd8-f28e-4786-ab96-9950f0a78031
    abobrov
     
  • the consistency in the replication topology in the (hopefully) rare case
    when hardware failure or software bugs could break it (issue 788 and 791)
    
    There are several parts in this commit :
    - a new log file called replication was added.
      It's purpose is to store all the consistency errors detected by the replication
      with enough information to allow the administrator to repair the problem.
      This file is configured by default and contain only the replication errors,
      To achieve the a new log severity keyword "None" has been created so that
      the associated error log publisher does not print any error not related to
      replication. (I will update the reference guide after this commit)
    
    - a new control (the replication repair control) has been added.
      When this control is used in a MODIFY, DELETE, ADD or MODDN operation
      the operation is marked as a non-replicated replication operation.
      This cause the following :
      - The operation is allowed to modify attributes that are normally not
        allowed to be modified or added (NO-USER-MODIFCATION) such as
        entryuuid and ds-sync-hist
       To achieve this I add to move those checks from the
        AddOperationBasis.getObjectClasses() or AddOperationBasis.getUserAttributes()
        to the LocalBackendWorkflowElement.processAdd() but this has already
        been reviewed.
      - no change number is associated to the operation.
      - the operation is not published to the replication server and is therefore
        a local only operation.
      - the replication don't try to solve conflict or generate historical information
        for this operation.
     
    The intended usage of this control is that the administrator will check
    for errors in the replication log, determine the entries that have inconsistent
    values and use the control to repair them.
    I will write some documentation explaining in more details how to do this.
    
    - even though this is not related to replication repair I also took advantage of
      this change to add the multimaster replication synchronization provider
      in the default configuration.
      This will make configuration of replication using dsconfig easier because
      the user will now only need to configure the replication servers and
      replication domains.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2687 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2686 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

19 Aug, 2007

4 commits

  • These tests provide full unit test coverage for all existing entry cache implementations.
    Some of the test methods reside in "slow" group so that they are skipped for precommit
    and alike while all implementation test classes belong to "entrycache" group in order to
    provide selective entry cache tests scope.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2685 41b1ffd8-f28e-4786-ab96-9950f0a78031
    abobrov
     
  • - fix bugs found by entry cache unit tests.
    - sanitize backend map maintenance.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2684 41b1ffd8-f28e-4786-ab96-9950f0a78031
    abobrov
     
  • initialized and contains the parent entry, since some JMX test methods assume
    that to be true.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2683 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • A new global property has been added to be able to specify to use a ClassLoader 
    that limits the search of the bundles to the jar containint the Messages class i
    f we are running WebStart setup/upgrader.  This property is only set in the quic
    ksetup.properties file, so the current behavior is preserved for all the other m
    essages files.  The MessageDescriptor constructors have also been modified and n
    ow require a ClassLoader as parameter.  With this modifications we have a ClassL
    oader defined in QuickSetupMessages.java that will only be used if we are runnin
    g QuickSetup.  The JnlpProperties have been moved to SetupUtils so that the mess
    ages classes only depend on classes on the org.opends.server classes that can be
     compiled independently.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2682 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

18 Aug, 2007

2 commits


17 Aug, 2007

16 commits


16 Aug, 2007

2 commits