25 Jun, 2009

3 commits


23 Jun, 2009

1 commit


22 Jun, 2009

6 commits


20 Jun, 2009

2 commits


19 Jun, 2009

4 commits


17 Jun, 2009

1 commit


16 Jun, 2009

1 commit

  • The fix consists on adding three new elements to the control panel.
    
    1. Allow the user to specify a future date when the backup will be launched or a periodic schedule to launch the backup.
    
    2. Allow the user to specify a future date when an export to LDIF will be launched or a periodic schedule to launch the export.
    
    3. Allow the user to see the scheduled and ongoing tasks.  This is a graphical equivalent of the manage-task command.  In this first version, the GUI displays the tasks and allows to cancel them.  It allows to display all the common task attributes in a table and also the specific attributes for a task in a separate pane.
    
    With this proposal including the possibility of allowing scheduling other type of tasks (like import or restore) is just a matter of adding half a dozen of lines of code (since most of the code is in StatusGenericPanel) so if we find that allowing scheduling tasks for other tasks (apart from backup and export) makes sense, it is pretty straightforward to add this functionality.
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5458 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

15 Jun, 2009

3 commits


13 Jun, 2009

4 commits


12 Jun, 2009

2 commits


11 Jun, 2009

3 commits


10 Jun, 2009

1 commit


09 Jun, 2009

1 commit

  • The limitations of the control panel when managing a remote server compared to managing the local instance are:
    
    - It cannot start/stop/restart the server
    - It cannot manage the server and update the server when it is off-line.
    - It cannot update the java settings.
    - It cannot update/view the windows service settings.
    - It cannot verify indexes.
    
    The main changes at the user interaction level are that the first dialog that is displayed proposes the user to manage the local instance or the remote instance.  Moreover the user can choose to change the managed instance by selecting a new menu Item ('File'/'Server to Administer...').
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5426 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

08 Jun, 2009

2 commits


05 Jun, 2009

3 commits


04 Jun, 2009

1 commit


03 Jun, 2009

1 commit

  • When replication is configured and when the connection between the Directory Server
    and the Replication Server fails the Directory Server is reconnecting to a Replication Server.
    However currently the error 53 (DSA is unwilling to perform) is returned to application
    during the time of the reconnection.
    This is wrong because at this time the DS is not on error.
    
    With this change the update threads now waits for the new connection to
    be established (which is fast) before being processed. 
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5408 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     

28 May, 2009

1 commit

  • When the replication heart-beat fails, the replication disconnects from the
    replication server and reconnect to another one.
    
    In such case the error messages are too verbose and may lead to false conclusion.
    This change reduce the error messages logged in those case. 
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5397 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato