org.forgerock / org.forgerock.opendj

19 Jan, 2009

5 commits

17 Jan, 2009

4 commits

16 Jan, 2009

4 commits

15 Jan, 2009

5 commits

14 Jan, 2009

4 commits

13 Jan, 2009

4 commits

12 Jan, 2009

4 commits

  • 633e67fd   Issue 3710 (control-panel: error when creating an new base dn with automatically generated data) ... Browse Code » 
    Although it is marked as a control panel issue, the bug is on the core server and applies also to the import-ldif command-line.

The code is trying to build the path to the MakeLDIF resource directory by using the server root (install root) instead of the instance root. The MakeLDIF resource directory is located under <root>/config/MakeLDIF and so the instance root must be used.



git-svn-id: https://svn.forgerock.org/opendj/trunk@4835 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • d7aca5db   Fix for issue #2829 (Problems configuring and unconfiguring replication servers) ... Browse Code » 
    scenario:
 1) configure and start 2 servers s1 and s2
 2) enable the replication between them
 3) disable replication on server s1
 4) disable replication on server s2
 5) re-enable the replication between them

we've got an error on step 5

The root cause is actually on step 3, when the replication is disabled
on server s1: all references to s1, including the s1 public instance
key, are removed from "cn=admin data" on all servers. To do that, we
just remove the info on one server, and the replication protocol will
propagate it on all the other.
The drawback (actually the issue) is that this public instance key is
indirectly used by several components. At least, the replication
protocol itself required the key to establish the connection between
replication servers on s1 and s2.
So, when we try to re-enable the replication the s1 public instance
key cannot be found and we've got the error.


fix:
At the end of the disable-replication process, we add again the
previously removed public instance key. 



git-svn-id: https://svn.forgerock.org/opendj/trunk@4833 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     
  • 4c12bc4a   Fix broken build. ... Browse Code » 
    
git-svn-id: https://svn.forgerock.org/opendj/trunk@4832 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • 319a6af5   Fix for issue 3709 (control-panel: value of "Backup Path" field should be the in… ... Browse Code » 
    …stance path and not the installation path in the Backup/Restore panels)
The code has been update to use the instance path instead of the install path in different places (the default backup directory, the path to be used to retrieve the java properties file, etc.).
If we are dealing with a package installation (install and instance paths are different), the control panel and the status command-line will display two paths: one for the install and the other for the instance.


git-svn-id: https://svn.forgerock.org/opendj/trunk@4831 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

10 Jan, 2009

1 commit

  • 96c4a9a1   Fix for issue 3701 (The Setup is not managing properly the backends when the rep… ... Browse Code » 
    …lication involves multiple base-dn)

With this fix the setup tries to use the same backend configuration of the servers that is replicating withFix for issue 3701 (The Setup is not managing properly the backends when the replication involves multiple base-dn)

With this fix the setup tries to use the same backend configuration of the servers that is replicating with.  So, if all the base DNs are on the same backend of the remote server, all the base DNs will be on the same backend of the server that is being setup.  If the base DNs are in different backends, the setup will create a backend for each base DN.


git-svn-id: https://svn.forgerock.org/opendj/trunk@4830 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

09 Jan, 2009

6 commits

08 Jan, 2009

1 commit

07 Jan, 2009

2 commits