org.forgerock / org.forgerock.opendj

22 Jul, 2009

2 commits

21 Jul, 2009

1 commit

20 Jul, 2009

1 commit

17 Jul, 2009

2 commits

15 Jul, 2009

4 commits

14 Jul, 2009

2 commits

  • 3270c04f   Store the exception when reading replication monitoring information at the serve… ... Browse Code » 
    …r descriptor level and not at the TopologyCache object level.


git-svn-id: https://svn.forgerock.org/opendj/trunk@5548 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • 56e9a98d   Follow up to fix for issue 4092 (dsreplication should allow to configure servers… ... Browse Code » 
    … with no replication server and servers with only a replication server)

With the fix of 4092, the replication monitoring information for a given replication domain may not be anymore under cn=monitor of the server where the domain is configured.  The replication monitoring information is only under cn=monitor of the replication servers.

The following changes wait till all the configuration has been loaded and after that tries to find the replication monitoring information by only searching on the replication servers.  If the server does not calculate the whole cn=monitoring tree when a request is made to cn=monitor, the new code should be more efficient than the previous one (since only searching in one replication server should be enough).  If it is not the case and the whole cn=monitor is recalculated when a search is made on it, then the new code only adds a new search in most of the cases (the worst case is the one when there are disjoint replication topologies under the same ADS with different replication servers, which is pretty rare).


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

13 Jul, 2009

3 commits

10 Jul, 2009

4 commits

09 Jul, 2009

2 commits

08 Jul, 2009

5 commits

07 Jul, 2009

8 commits

06 Jul, 2009

1 commit

  • ea7b06cd   Fix for issue 4092 (dsreplication should allow to configure servers with no repl… ... Browse Code » 
    …ication server and servers with only a replication server)

The new arguments for the enable subcommand are:
--noReplicationServer1
    Specifies not to have a replication port and changelog on the first server.
    The first server will only contain replicated data but no changelog with
    the modifications made to the replicated data.  At least two servers with a
    changelog are required in the replication topology to avoid a single point
    of failure
--onlyReplicationServer1
    Specifies to only have a changelog (with a replication port) on the first
    server.  The first server will not contain replicated data but only a
    changelog with the modifications made in the data contained in other
    servers
--noReplicationServer2
    Specifies not to have a replication port and changelog on the second
    server.  The second server will only contain replicated data but no
    changelog with the modifications made to the replicated data.  At least two
    servers with a changelog are required in the replication topology to avoid
    a single point of failure
--onlyReplicationServer2
    Specifies to only have a changelog (with a replication port) on the second
    server.  The second server will not contain replicated data but only a
    changelog with the modifications made in the data contained in other
    servers


The two new arguments for the disable subcommand are:

--disableReplicationServerArg
    Disable the replication server.  The replication port and changelog will be
    disabled on the specified server
--disableAll
    Disable all the replication configuration in the specified server.  The
    contents of the server will no longer be replicated and the replication
    server (changelog and replication port) will be disabled if it is
    configured

There is a new configuration argument:
--advanced
    Use this option to have access to advanced settings when running this
    command-line in interactive mode


Note that the --disableAll is not required but it can be considered a handy option to remove all replication information in a given server (including the contents in cn=admin data).  It can be useful when the user wants to start over a replication configuration as it guarantees a clean starting point.

The current behavior (when no new arguments are specified) has been kept intact.  This means that the user will not have to choose to configure the replication server or the domains unless the advanced option is specified.

The exception to this happens in the case where the user decides to disable all the suffixes (but the new --disableAll option is not specified).  In this case the replication server will not be automatically disabled.  However if the command is run in non-interactive mode, the user will be informed of this and if run in interactive mode, the user will be proposed to disable it.

The status subcommand has also been modified to display the cases where there are replication servers that are no domains and vice-versa.


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

04 Jul, 2009

1 commit

03 Jul, 2009

1 commit

02 Jul, 2009

2 commits

01 Jul, 2009

1 commit

  • 561a559e   Fix for issue 4080 (Using Quicksetup jnlp link: OpenDS splashscreen is displayed… ... Browse Code » 
    … during a long while)

The problem comes because quicksetup.jar contains the utility properties.  The code tries to load the correct bundle for the preferred language (for ES), since it is not in quicksetup.jar (no messages_en is included), waits till all the jars are downloaded.  This makes the splashscreen to stay till all the jars are downloaded.

In fact this can be considered a duplicate of  2112.  The fix consists on marking utility.properties the same as quicksetup.properties: when the server is launched using java web start it will use a particular class loader.


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