org.forgerock / org.forgerock.opendj

26 Jun, 2007

8 commits

  • 5e4e8e94   updated xml files to point to shared/stax.dtd ... Browse Code » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2180 41b1ffd8-f28e-4786-ab96-9950f0a78031
    al_xipe
     
  • 0638f7e8   updated xml files to point to shared/stax.dtd ... Browse Code » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2179 41b1ffd8-f28e-4786-ab96-9950f0a78031
    al_xipe
     
  • 152aaa40   updated xml files to point to shared/stax.dtd ... Browse Code » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2178 41b1ffd8-f28e-4786-ab96-9950f0a78031
    al_xipe
     
  • b7814061   updated xml files to point to shared/stax.dtd ... Browse Code » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2177 41b1ffd8-f28e-4786-ab96-9950f0a78031
    al_xipe
     
  • a9881666   This change introduce a new configuration attribute that allow to configure ... Browse Code » 
    the behavior of the server when replication has been configured but the
replication have not been able to connect to any of the configured replication server.

This configuration attribute is named stays in the replication domain
configuration entry and is named : ds-cfg-isolation-policy

The possible behavior values are :
- reject-all-updates : When this value is used and the server cannot connect to
 any of the replication server, all the updates are rejected with an
 UNWILLING TO PERFORM error code.
 This is the default value
- accept-all-updates :  When this value is used and the server cannot connect to
 any of the replication server, all the updates are accepted without sending them to
 a replication server, when a replication server  will become available, the server will
 use the historical information to generate replication messages.
 This last mode will make the changes at risk because they will only be saved in
 the historical information of the local server. It may also introduce high replication
 delay when the connection establish again.
 Note that currently the replication code is not yet able to generate messages for the
 MODDN, DELETE and ADD operations. (issue 1752)

This change also improve the error messages that are logged when the server cannot connect
any replication : before the server was continuously logging messages twice per seconds, now
the server only logs the error the first time and log a new message indicating that everything is
fine when a replication server is back.


git-svn-id: https://svn.forgerock.org/opendj/trunk@2176 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • 9e2cc845   Added the call to run the indexes test suite ... Browse Code » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2175 41b1ffd8-f28e-4786-ab96-9950f0a78031
    al_xipe
     
  • 19399343   stax 3.2.2 DTD ... Browse Code » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2174 41b1ffd8-f28e-4786-ab96-9950f0a78031
    al_xipe
     
  • e95bace2   first commit for the indexes test suite ... Browse Code » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2173 41b1ffd8-f28e-4786-ab96-9950f0a78031
    al_xipe
     

25 Jun, 2007

9 commits

24 Jun, 2007

5 commits

23 Jun, 2007

2 commits

  • 95deb96c   Migrate the core configuration to the admin framework. ... Browse Code » 
    
git-svn-id: https://svn.forgerock.org/opendj/trunk@2158 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • 34309988   Provide a way to control the order in which plugins are invoked. This ... Browse Code » 
    implementation is similar to that used by DSEE 6.  The "cn=Plugins,cn=config"
configuration entry now supports a number of new configuration attributes
(one per plugin type) that can be used to control the invocation order for
plugins of that type.  The plugin order specification should be a string that
is a comma-delimited list of the names of the plugins in the order in which
they should be invoked, and it should also include an asterisk to indicate
the order in which any unmatched plugins should be invoked.

For example:

     ds-cfg-plugin-order-pre-operation-add: Entry UUID, *

This indicates that the "Entry UUID" plugin should be invoked before any other
pre-operation add plugins.

The plugin order is evaluated only at startup, and any problems or
inconsistencies detected (e.g., the same plugin name listed twice in the order,
or a plugin order that does not contain a wildcard character) will generate
warning messages in the server's error log.

OpenDS Issue Number:  253


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

22 Jun, 2007

8 commits

21 Jun, 2007

8 commits