23 Aug, 2007

9 commits


22 Aug, 2007

13 commits

  • …ration was incorrectly called "base-level"
    
    Fix for issue 2134
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2748 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2747 41b1ffd8-f28e-4786-ab96-9950f0a78031
    mkeyes
     
  • …tedResult, in the function, searchStringForSubstring.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2746 41b1ffd8-f28e-4786-ab96-9950f0a78031
    mkeyes
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2745 41b1ffd8-f28e-4786-ab96-9950f0a78031
    mkeyes
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2744 41b1ffd8-f28e-4786-ab96-9950f0a78031
    mkeyes
     
  • …rguments that allow the task to be scheduled to run in the directory server's JVM through the task interface as well as through the existing method or operating within the running JVM.
    
    - This introduces several classes that handle the plumbing of scheduling a task:
    
    LDAPConnectionArgumentParser:  an argument parser that comes pre-populated with the common options used to specify an LDAP connection and includes a method for creating a connection
    
    TaskScheduleInformation:  source of information important for creating the scheduled task entry in the backend
    
    TaskScheduleClient:  interacts on behalf of clients that wish to schedule tasks
    
    TaskTool:  base class that the tools can implement to handle decision about whether to operate locally or remotely
    
    - For export-ldif I removed the short identifier -w for the wrap options since it conflicted with the -w password option.
    
    - For import-ldif I removed the short identifiers -K for skipFile and -q for quiet since they conflicted with the options for specifying the keystore path and startTLS options respectively. 
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2743 41b1ffd8-f28e-4786-ab96-9950f0a78031
    kenneth_suter
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@2742 41b1ffd8-f28e-4786-ab96-9950f0a78031
    kenneth_suter
     
  • More refactoring to account for the new parameter, expectedResult, in the searchStringForSubstring function.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2741 41b1ffd8-f28e-4786-ab96-9950f0a78031
    mkeyes
     
  • When using the setup to configure 2 servers in multimaster mode.
    The setup first creates the configuration of the first server and start it
    When the second setup is run to configure the second server, the setup updates
    the configuration of the replication-server on the first server, however the code for handling this dynamic configuration was not yet written and this
    information is not taken into account.
    
    The replication servers are therefore not connected and the replication server
    on the new host therefore does not get the updates.
    
    These changes implement the dynamic configuration of replication servers so that
    the same scenario works fine.
    
    The only properties that is now not dynamically configurable is the
    path of the changelog database.
    
    A new test has been added for these changes.
    I've also tested manually that this does fix the replication server problem
    after configuration using the setup program. 
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2740 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2739 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gary_williams
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2738 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gary_williams
     
  • The replication monitoring information already provides the
    attribute unresolved-naming-conflicts that counts the number of conflicts
    that was not automatically resolved since last startup.
    
    The conflicting entries are also marked with the ds-sync-confict attribute
    so that administrators can look for these entries 
    using filter ds-sync-confict=*
    
    This code add the generation of an administrative alert when a conflict is
    detected so that administrators can be made aware of the problem.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2737 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • Before this fix, If one remove the root entry of a replication domain,
    then stop the server The PersistentServerState is lost.
    Therefore when later restarting the server all the changes from
    the replication server are replayed on the database.
    
    To avoid this the fix is simply to store the PersistentServerState to the configuration entry when the root entry does not exist.
    
    I have not developed a unit test for this scenario because I believe that it is not possible to restart the server during the unit test.
    I have done manual tests to check that the PersistentServerState
    is correctly saved and reread. 
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2736 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     

21 Aug, 2007

16 commits


20 Aug, 2007

2 commits